TELES VoIPBOX BRI 14.0

Software version 14.
0
TELES.VoIPBOX BRI
2
Chapter 1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.1 organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2 Safety and Security Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2.1 Safety Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.2 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.3 Instructions for Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.4 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Jacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Tips for EMC Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5 System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5.1 Protecting the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6 CDR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.7 Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
3.1 Whats New in Version 14.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3 Implementation Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 4 VoIPBOX BRI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
4.1 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 VoIPBOX BRI Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.1 ISDN Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2 Ethernet Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5 Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.6 Hardware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.7 LED Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.8 Startup with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.8.1 Installing Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.8.2 Configuration with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.9 Startup via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.10 Self Provisioning with NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.11 Remote Access and Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.11.1 GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.11.2 HTTP User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
table of contents
3
4.11.3 FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.11.4 Setting a Password for Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 5 Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
5.1 Configuration File ip.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1.1 System Section Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.2 Ethernet Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.3 Bridge Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1.4 NAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.5 PPPoE Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.1.6 Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1.7 Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.1.8 DHCP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1.9 PPP Configuration for ISDN Dial-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.1.10 VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1.11 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Active Ethernet Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Integrated DSL-Router Scenario for VoIP Traffic with an Active DHCP Server and Firewall . . . . . . . . 41
VLAN Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2 Configuration File pabx.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.1 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Bypass Relay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Night Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.2 SMTP-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2.3 SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2.4 Time-Controlled Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3 Configuration File route.cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3.1 Entries in the Sections [System] and [Night<num>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Restrict. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.3.2 VoIP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.3.3 Gatekeeper Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.3.4 Registrar Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.5 Radius Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4
Chapter 6 Routing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
6.1 VoIPBOX BRI as a Second-Generation LCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.2 VoIPBOX BRI in an H.323 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.3 Work@Home Scenario with Signaling through a SIP Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.4 ISDN Dial-Up for Terminating VoIP Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.5 Backbone Router Using a Backup Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.6 Backbone Router with Direct Endpoint Signaling (H.323) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.7 IntraSTAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.8 Backbone Router and Authentication and Accounting with a Radius Server. . . . . . . . . . . . . . . . 76
6.9 VoIP Backup and Automatic Reactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 7 System Maintenance and Software Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
7.1 Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.2 Status and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.3 Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.4 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.4.1 ISDN Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.4.2 VoIP Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Interface IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
RTP/RTCP Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Internal Protocol Interface (to ISDN, POTS, Mobile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
H.245 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
RAS (Registration, Admission, Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ENUM Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
7.4.3 Remote Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7.4.4 SMTP Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7.4.5 Number Portability Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.4.6 DTMF Tone Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 8 Signaling and Routing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
8.1 IntraSTAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.2 Digit Collection (Enblock/Overlap Receiving). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.3 Rejecting Data Calls and Specified Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8.3.1 Blacklist Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8.3.2 Whitelist Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8.3.3 Rejecting Calls with ISDN Bearer Capability Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
8.3.4 Specific Routing of Data Calls via VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
8.4 CLIP and CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.4.1 Routing CLIP and CLIR Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.4.2 Setting CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.4.3 Setting CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5
8.5 Conversion of Call Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
8.6 Setting Number Type in OAD/DAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
8.7 Setting the Screening Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
8.8 Setting a Default OAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
8.9 Setting Sending Complete Byte in Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
8.10 Miscellaneous Routing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.10.1 Routing Calls without a Destination Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.10.2 Routing Calls Based on Existence of Destination Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.10.3 Changing Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 9 Least Cost Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
9.1 Carrier Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
9.1.1 Routing Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
9.2 Alternative Routing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.3 Charge Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.4 Generating Charges with the VoIPBOX BRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 10 Online Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
10.1 ASR Calculation and Resetting Statistic Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.2 Generating and Retrieving CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
10.2.1 Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
10.2.2 Missed Calls List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
10.3 Generating Online CDRs via E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Chapter 11 DLA/Callback Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
11.1 Call Connector and Callback Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.1.1 Special Announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.2 DLA with DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.1.3 DLA with Fixed Destination Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.4 Callback with DTMF and OAD as Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.1.5 Callback with DTMF and PreConfigured Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.6 Callback to OAD and Fixed Second Leg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.1.7 DLA with DTMF and PIN for First Leg and Callback for Second Leg . . . . . . . . . . . . . . . . . . . . . . . 152
11.1.8 Using a PIN in Front of the Call Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Chapter 12 Additional VoIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
12.1 Signaling Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
12.2 Location Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
12.3 Routing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
12.4 Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12.5 Compression Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
12.6 Fax/Modem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6
12.7 DTMF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Chapter 13 Optional Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
13.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
13.2 Http User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
13.3 iPBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
13.4 SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
13.5 DNS Forwarder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
13.6 ipupdate - DynDNS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
O R G A N I Z A T I O N
1
VoIPBOX BRI 14.0. Revised: 2008.
1 ABOUT T HI S MANUAL
This manual is set up to guide you through the step-by-step installation of your VoIPBOX BRI, so that you can follow
it through from the front to the back. Quick-installation instructions appear in Chapter 4.8, Startup with
TELES.Quickstart. Make sure you familiarize yourself thoroughly with the safety and security precautions detailed
in Chapter 2 before you begin to install your VoIPBOX BRI. TELES is not liable for any damage or injury resulting
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 BRI 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 BRI and its implementation scenarios.
Chapter 4, VoIPBOX BRI Installation contains information on how to connect and configure the
system so that it is ready for operation.
Chapter 5, Configuration Files describes the VoIPBOX BRIs individual configuration files and
parameters.
Chapter 6, Routing Examples contains useful examples and descriptions of scenario-based
configurations in the route.cfg.
Chapter 7, System Maintenance and Software Update describes system messages that are
saved in the protocol file, as well as trace options.
Chapter 8, Signaling and Routing Features describes configuration settings in the route.cfg
used for adjusting signaling and customizing the configuration for specific scenarios.
Chapter 9, Least Cost Routing describes configuration options for various routing processes.
Chapter 10, Online Traffic Monitor contains the configuration for monitoring the systems statistics
and CDRs.
Chapter 11, DLA/Callback Services contains money-saving features that expand the functionality
of your VoIPBOX BRI to include callback capability and DTMF services.
Chapter 12, Additional VoIP Parameters contains additional configuration entries to fine-tune
communication with the VoIP peer.
Chapter 13, 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.
Code file names, variables and constants in configuration files or commands in body text.
"conventions" on page 1 cross-references can be accessed in the PDF files by a single mouse click.
S A F E T Y S Y MB O L S
2
Configuration data or extracts are written in single-column tables with a gray background.
1 . 3 S A F E T Y S Y MB 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 discharge
Components at risk of discharge must be grounded before being touched.
i i
! !
! !
S A F E T Y ME A S U R E S
CHAPT E R 2
3
2 SAF ET Y AND SECURI T Y PRECAUT I ONS
Please be sure and take time to read this section to ensure your personal safety and proper operation of your
VoIPBOX BRI.
To avoid personal injury or damage to the system, please follow all safety instructions before you begin working
on your VoIPBOX BRI.
VoIPBOX BRIes 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 ME A S U R E S
Danger of electric shock - the power supplies run on 230 V. Do not open the VoIPBOX BRI or its power supply.
Make sure to install the VoIPBOX BRI 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.
2 . 2 P O WE R S U P P L Y
The included power supply is to be used exclusively for operation of your VoIPBOX BRI.
2 . 2 . 1 TE 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 BRI
Input voltage: 230V~ +/-15% 50-60Hz; 0.40A
Output voltage: 12V ---; 1.6A
Weight: 96g
Tested and certified as per EN60950-1
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 contents
of your VoIPBOX BRI.
i i
P O WE R S U P P L Y
CHAPT E R 2
4
2 . 2 . 2 S Y MB O L S
The symbols on the power supply have the following meanings:
2 . 2 . 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 capacity
for your VoIPBOX BRI.
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 time.
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.
Use only the power supply GSP-1216TLS/1 included in the package contents of your
VoIPBOX BRI.
o - + + - o
i i
J A C K S
CHAPT E R 2
5
2 . 2 . 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/or
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 35C.
Do not use the device if it is damaged or if there are signs of misfunction. In this case, send it to TELES
Service or dispose of it properly (not with the public trash).
2 . 3 J A C K S
The jacks on the VoIPBOX BRI have fulfilled the requirements of the SELVsafety standard.
2 . 4 T I P S F O R E MC P R O T E C T I O N
2 . 5 S Y S T E M S E C U R I T Y
This section describes all points crucial to the VoIPBOX BRIs system security.
The VoIPBOX BRIs location must support normal operation according to EN ETS 300 386. Be sure to select the
location with the following conditions in mind:
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, the site should be air-conditioned. The site must be free of strong electrical or
magnetic fields, which cause disrupted signals and, in extreme cases, system failure.
! !
C D R F I L E S
CHAPT E R 2
6
Servicing the VoIPBOX BRI
Regular servicing ensures that your VoIPBOX BRI runs trouble-free. 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.
2 . 5 . 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 resulting
from or in relation to such changes. Please thoroughly check any changes you or a third party have made to your
configuration!
Make sure your hard disk or flash disk contains enough storage space. Downloading the log files and deleting them
from the VoIPBOX BRI on a regular basis will ensure your VoIPBOX BRIs reliability.
Be careful when deleting files that you do not delete any files necessary for system operation.
2 . 6 C D R F I L E S
Call Detail Records are intended for analysis of the VoIPBOX BRIs activity only. They are not designed to be used
for billing purposes, as it may occur that the times they record are not exact.
Temperature: The site must maintain a temperature between 0 and 35C. Be sure to
guard 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 on
the label.
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 acti-
vated.
! !
i i
N E T WO R K S E C U R I T Y
CHAPT E R 2
7
2 . 7 N E T WO 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 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 BRI if you connect it to the Internet:
Use an application gateway or a packet firewall.
To limit access to the VoIPBOX BRI to secure remote devices, delete the default route and add individual
secure network segments.
Access to the VoIPBOX BRI via Telnet, FTP or 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.
The firewall must support the following features:
Protection against IP spoofing
Logging of all attempts to access the VoIPBOX BRI
The firewall must be able to check the following information and only allow trusted users to access the
VoIPBOX BRI:
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 Port
For all systems except vGATE
FTP TCP 21 (default, can be set)
Telnet (for TELES debug access
only)
TCP 23
SMTP TCP 25
DNS forward UDP 53
HTTP TCP 80 (default, can be set)
SNTP UDP 123
SNMP UDP 161
CHAPT E R 2
8
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)
TELES.vGATE Control Unit
TCP 57343
vGATE tunneling TCP 4446
For TELES.vGATE Control Unit and iMNP
FTP TCP 21
Telnet TCP 23
MySQL database TCP 3306
iGATE or VoIPBOX GSM/
CDMA 4 FX to vGATE
TCP 57342
vGATE tunneling to iGATE or
VoIPBOX GSM/CDMA 4 FX
TCP 4446
CDMA 4 FX to iMNP
TCP 9003
Remote vGATEDesktop TCP 57344
Remote vGATEDesktop (read only) TCP 57345
iMNP TCP 9003
For vGATE SIM Unit
TELES.vGATE Control Unit plus
CDMA 4 FX
TCP 51500
For NMS
FTP TCP 21
Telnet TCP 23
Table 2.2 Default Ports Used for Specific Services (continued)
CHAPT E R 2
9
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)
WH A T S N E W I N V E R S I O N 1 4 . 0
CHAPT E R 3
10
3 OVERVI EW
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 net-
work and vice versa. Incoming traffic arrives at one VoIPBOX BRI, which routes the calls accordingly, depending
on the calls destination and attributes.
3 . 1 WH A T S N E W I N VE R S I O N 1 4 . 0
Enhanced HTTP user interface including Wizard for easy configuration
New SIP settings:
VoipSdpProxy=<mode>: enables transmission of all SDP parameters if a call is from SIP to SIP
VoipUseRad=<mode>: different addresses in request header and To field result in redirected ISDN
number
Customized translation of DSS1 cause values to SIP events
Supports 3G faxes
Configurable time interval for echo detection in VoIP
New configuration settings for VoIP DTMF tone handling
Expanded functionality of integrated DLA/callback server
Integrated mail client capable of SMTP authentication
CDR enhancement with new output for VoIP calls (codec, ptime)
3 . 2 F E A T U R E S
VoIP
8 media channels
H.323 v.4 / SIP v.2 signaling (RFC 3261), operating in parallel
Various audio codecs: G.711, G.723.1, G.726, G.728, G.729, GSM, iLBC, Fax T.38, Data: clear channel
RTP multiplexing (reduces bandwidth required for RTP data by up to 60%)
ENUM client
Echo cancellation G.1682000
Silence suppression, comfort noise generation, voice activity detection
Support for multiple gatekeepers and multiple registrars
STUN client
Traffic shaping
ISDN
2 & 4 BRI ports, TE or NT
DSS1 (Q.931),Q.SIG-BC; PP or PMP
I MP L E ME N T A T I O N S C E N A R I O S
CHAPT E R 3
11
LCR Engine
Multiple VoIP-carrier logins
Multiple PSTN routing methods
Multilevel alternative routing
Dynamic fallback to PSTN
Lifeline functionality on power loss or system failure
General
User-friendly HTTP user interface 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
3 . 3 I MP L E ME N T A T I O N S C E N A R I O S
These are the most commonly used implementation scenarios:
VoIP Gateway
The VoIPBOX BRIes sophisticated routing al-
gorithms allow VoIP communication via SIP
server and/or gatekeeper (H.323), as well as
multi-destination operation without a SIP Serv-
er or gatekeeper. Various voice codecs ensure
universal connection to different VoIP destina-
tions. Fax transmission occurs via T.38 or fall-
back to G.711a. Backup routes can be
activated in case of VoIP peer failure. After a
defined amount of time, the VoIPBOX BRI re-
sumes its primary route.
LAN
VoIP
Carrier
4 x BRI
Ethernet
I MP L E ME N T A T I O N S C E N A R I O S
CHAPT E R 3
12
Least Cost Router 2nd Generation
The VoIPBOX BRIs sophisticated routing algo-
rithms serve as an LCR between your PBX and
the PSTN or VoIP carrier. Internet connection
can occur via integrated DSL router. The sys-
tem reverts to ISDN if there is an IP connection
failure.
LAN VoIP
Carrier
2 x BRI
Ethernet
2 x BRI
PSTN
C H E C K L I S T
CHAPT E R 4
13
4 VOI PBOX BRI I NST AL L AT I ON
This section contains information on basic installation and configuration of your VoIPBOX BRI. Follow the easy in-
structions to set up your VoIPBOX BRI 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.
4 . 1 C H E C K L I S T
The following checklist provides step-by-step installation instructions.
1. Check the package contents
2. Install the device
3. Connect the BRI lines to the PBX and/or the PSTN
4. Check functionality (using the LEDs)
5. Using Quickstart, set the configuration (IP address and BRI / VoIP configuration)
6. Secure the LAN connection
7. Secure connection with the configuration program
4 . 2 PA C K A GE C O N T E N T S
Your VoIPBOX BRI package contains the following components. 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:
1 VoIPBOX BRI
1 power supply
4 RJ-45 ISDN cables (black)
1 RJ-45 LAN cable with gray connectors
V O I P B O X B R I H A R D WA R E D E S C R I P T I O N
CHAPT E R 4
14
4 . 3 VO I P B OX B R I H A R D WA R E D E S C R I P T I O N
The VoIPBOX BRI handles traffic on up to 8 media channels. The following pages describe installation of the
VoIPBOX BRI.
Figure 4.1 shows the front and rear view of a VoIPBOX BRI.
4 . 4 I N S T A L L A T I O N R E Q U I R E ME N T S
Before installing your VoIPBOX BRI, make sure you have the following connections in place:
Ethernet connection
ISDN BRI connection to PBX and/or to the PSTN
Power
4 . 4 . 1 I S D N WI R I N G
Figure 4.2 shows how the VoIPBOX BRI is connected between the PBX and PSTN.
The TE ports connect to the PSTN and the NT ports connect to the PBX. You can
connect the VoIPBOX BRI to a second ISDN outlet for the second ISDN interface.
Figure 4.1 VoIPBOX BRI: Front and Rear View
ISDN 1
TE/NT
12V
Power
Ready
L3 L4 L2
Ethernet ISDN
Ports
1 & 3
Red Green Green Green
ISDN 2
TE/NT
ISDN 3
NT
ISDN 4
NT
Ethernet
1
Ethernet
2
ISDN
Ports
2 & 4
Figure 4.2 VoIPBOX BRI Wir-
ing Scheme
Power TE 1 TE 2 NT 1 NT 2
PSTN PBX
I N S T A L L A T I O N R E Q U I R E ME N T S
CHAPT E R 4
15
Figure 4.3 shows the standard pin assignment for TE and NT modes. The cables included in the package contents
have this pin assignment. You must change the pin assignment if it differs on the connected equipment.

4 . 4 . 2 E T H E R N E T WI R I N G
To connect the VoIPBOX BRIs 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 BRI directly to your computer and a connection cannot be established after
you plug the cable in, use a cable with the following pin assignment:
7
8
3
4
5
6
Network
Interface
1
2
7
8
3
4
5
RX+
6
TX-
Terminal
Interface
1
2
TX+
TE NT
Abbreviations: TX - Transmit / RX - Receive
RX-
TX-
RX+
RX-
TX+
Figure 4.3 ISDN Wiring Scheme
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
P R E P A R I N G F O R I N S T A L L A T I O N
CHAPT E R 4
16
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 BRI requires a network connection. Please have the fol-
lowing information for connection to your network available:
IP address in your local network for the VoIPBOX BRI to be configured
Netmask for the VoIPBOX BRI to be configured
Default gateway for VoIPBOX BRI to be configured
DNS server address
NTP server address
4 . 6 H A R D WA R E C O N N E C T I O N
Connect your computer with the local network
Connect the VoIPBOX BRI with the local network
Using the ISDN connection cables included in the package contents, connect the VoIPBOX BRI with your
PBX and/or the PSTN according to the required port configuration.
Connect the VoIPBOX BRI with the power supply.
4 . 7 L E D F U N C T I O N A L I T Y
Each VoIPBOX BRI has the following status LEDs:
Bear in mind that the preconfigured VoIPBOX BRIs default IP address is 192.168.1.2.
If this IP address is already being used in your local network, you must run Quickstart
without a connection to your local network. This can occur using a back-to-back
Ethernet connection from your computer to the VoIPBOX BRI.
If the desired IP address for the VoIPBOX BRI is not in your network, you must assign
your computer a temporary IP address from this IP-address range.
Table 4.3 VoIPBOX BRI LEDs
LED Description
Red On:
The VoIPBOX BRI is active.
Blinking:
The VoIPBOX BRI is in startup mode.
Blinking fast:
The VoIPBOX BRI is not registered / connected with the SIP-carrier
1st Green Blinking:
Ethernet packets are being sent and received.
i i
S T A R T U P WI T H Q U I C K S T A R T
CHAPT E R 4
17
4 . 8 S T A R T U P WI T H Q U I C K S T A R T
Quickstart is an application that helps you to configure the basic settings of your VoIPBOX BRI quickly and conve-
niently.
Quickstart can be installed on any of the following operating systems:
Windows 98 SE
Windows NT
Windows ME
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 a
non-Windows operating system (e.g. Linux) follow the instructions in Chapter 4.9 .
2nd Green On:
Call is being transmitted from ISDN to VoIP.
3rd Green On:
Call is being transmitted from ISDN to ISDN.
Table 4.3 VoIPBOX BRI LEDs (continued)
LED Description
CHAPT E R 4
18
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 and
select Quickstart from the menu. Follow
the Windows instructions to begin instal-
lation of the Quickstart. Once installation
begins, click Next to install Quickstart in
the predefined folder. To install it in an-
other location, click Browse and select a
folder from the browser that appears.
Then click Next.
The next dialog asks you where you want
to install the programs icons. To install
them in the folder that appears, click
Next. If you want to install them in an-
other location, select a folder from the list
or enter a new folder name. Then click
Next.
To start Quickstart immediately following
installation, activate the checkbox I
would like to launch Quickstart. Make
sure the checkbox is inactive if you do not
want to start the program now. Click
Finish.
Figure 4.5 Quickstart Installation
CHAPT E R 4
19
4 . 8 . 2 C O N F I G U R A T I O N WI 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 BRI. Open Quickstart.exe. The program will automatically
search for your VoIPBOX BRI in the local network. For Quickstart, the source UDP port is 57445. It might be nec-
essary to change the firewall rules on your system.
Click the Search button to restart the search. When the program has found your VoIPBOX BRI, it will appear in
the main window. As soon as it appears, you can end the search by clicking Stop. The window on the right pro-
vides a 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. The
serial number appears as the systems name.
To change the appearance of the window, select Large Icons, Small Icons or Details from the View menu. In
the following description, we will use the Details View, which contains the following columns:
In the Options menu, you can suppress or activate ICMP ping to test the Internet connection.
Table 4.4 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.
CHAPT E R 4
20
To perform the initial configuration of the system, double-
click the icon or right-click and select Configure. The IP
Settings dialog will appear. If you are using a DHCP serv-
er, activate the checkbox DHCP. This will deactivate the
next four lines. Your DHCP server will automatically provide
all of the other necessary information. If you do not have a
DHCP server, leave the DHCP checkbox empty. The default
IP address appears in the IP Address box. Enter a new IP
address. If the address you enter already exists in the net-
work, you will be notified to choose another address at the
end of the configuration process. Enter the systems net-
mask in the Mask dialog box. Enter the IP address for the
Default Gateway and the Time Server in the corre-
sponding dialog boxes. Select the Time Zone for the loca-
tion of the system. Click Next.
In the VoIP Settings dialog, select H323 or SIP for the Sig-
naling protocol you would like to use for outgoing calls to
VoIP. H.323 and SIP are both accepted for incoming calls, re-
gardless of what you select here. If you select SIP, you can en-
ter a SIP User Name and a SIP Password. If you define a
username, a registrar profile will automatically be generated.
Enter the Peer IP Address. Set a Mask for incoming calls,
so that calls from all IP addresses in the range entered will be
accepted. Select the Compression codecs you would like to
use. All codecs listed are for voice transmission, except t38,
which is for fax transmission. Click Next.
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.7 Quickstart Configuration: IP Settings
i i
Figure 4.8 Quickstart Configuration: VoIP Settings
S T A R T U P V I A F T P
CHAPT E R 4
21
In the BRI Settings window, select the settings for each BRI
port. Select TE for terminal endpoint or NT for network ter-
mination. Select PMP or PP for Point-to-Multipoint or Point-
to-Point termination. Click Next.
In the Routing window, enter the Area Code, where the
system has been installed if you are using SIP. Select Gate-
way to send all incoming PSTN calls via VoIP. Select LCR if
the system is connected between a PBX and the PSTN. Spe-
cific numbers or prefixes defined here are routed to VoIP if
you select All to PSTN except or to PSTN if you select All
to VoIP except. All other calls to numbers not on the list are
routed from the PSTN or VoIP, depending on what you spec-
ify. Double-click in the Route to VoIP/PSTN dialog box to
enter the numbers that are to be routed to VoIP or PSTN.
Now the system is configured; all other processes run auto-
matically.
First the systems IP address will be changed and then the
system will start with the new IP address. When the system
can be reached at the new IP address, all PSTN ports and
routing entries will be set by sending the created configura-
tion files to the system.
If you right-click the systems icon in the main window, you can also choose Temporarily Configure IP Address,
only the IP address for the systems first Ethernet interface and the netmask will be temporary changed. This can
be helpful if you want to set up local remote access to the system and use other IP settings on the remote device
than the systems IP configuration in the network. Bear in mind that the functions on the systems first Ethernet
interface work with the new settings.
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 via
FTP. 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.
Figure 4.9 Quickstart Configuration: BRI Settings
Figure 4.10 Quickstart Configuration: Routing
S E L F P R O V I S I O N I N G WI T H N MS
CHAPT E R 4
22
The default user is teles and the default password is tcs-ag. To configure the system, use the default config-
uration file example on the CD in the Configfiles directory and the following subdirectories:
IPconfig
This subdirectory contains the file (ip.cfg) responsible for configuration of the Ethernet interface
4xnt
All ISDN ports are configured in NT mode. The VoIPBOX BRI acts only as a VoIP gateway.
3xnt1xte
The first port is configured in TE mode and the other three in NT mode. The VoIPBOX BRI acts as VoIP LCR.
2xnt2xte
The first two ports are configured in TE mode and the other two in NT mode. The VoIPBOX BRI acts as VoIP
LCR.
To edit the default configuration, follow the directions in Chapter 5 . Upload the configuration files into the /
boot directory.
4 . 1 0 S E L F P R O V I S I O N I N G WI T H N MS
With a management connection to the NMS (Network Management System), the VoIPBOX BRI can retrieve its con-
figuration files from the configured NMS. That means that custom configuration of the device occurs automatically
when the device is started. The following setting must be made in the [System] section of the pabx.cfg:
AlarmCallback=<ip address NMS server>
RemoteCallback=<ip address NMS server> <time> <days of week + holiday>
As soon as the device is started, it connects automatically with the NMS, which uses the devices TAG number to
send a prepared configuration. For further information on configuration of the NMS, please refer to the NMS Sys-
tems Manual.
4 . 1 1 R E MO 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 can
occur with the GATE Manager (Chapter 4.11.1 ), the HTTP user interface (Chapter 4.11.2 ), or via FTP
(Chapter 4.11.3 ).
R E MO 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
CHAPT E R 4
23
4 . 1 1 . 1 G AT E MA N A GE R
Figure 4.11 GATE Manager
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.
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.
Use the CD enclosed in your package contents to install the GATE Manager. For a detailed description of installa-
tion and implementation of the GATE Manager, please refer to the GATE Manager and Utilities Programs Manual.
GATE Manager remote access can occur via IP or ISDN. GATE Manager access via IP uses port 4444 as origination
TCP port and port 4445 as destination port. The following default value (4445) is configured in the pabx.cfg
file for the systems port:
In the default configuration, ISDN access is disabled. To configure the system so that certain data calls are received
as remote administration calls, make the following changes in the pabx.cfg:
RemoteCode=BBB
MapAll<num>=BBB DATA
MoipPort=4445
CHAPT E R 4
24
Make the following entries in the route.cfg if the system is to handle all data calls as remote-administration
calls:

For a detailed description of ISDN configuration, see the TELES Infrastructure Systems Parameters and Hardware
Manual.
4 . 1 1 . 2 H T T P U S E R I N T E R F A C E
Figure 4.12 HTTP User Interface
Remote access can occur via the HTTP user interface. Even users with little experience can easily configure standard
system settings with this interface. Simply open a browser and enter the systems IP address in the address bar.
The following administrative levels apply:
Carrier Mode (Full Access)
User: teles-carrier
MapAll0=BBB DATA
MapAll1=BBB DATA
MapAll2=BBB DATA
MapAll3=BBB DATA
MapAll4=BBB DATA
MapAll5=BBB DATA
MapAll6=BBB DATA
MapAll7=BBB DATA
MapAll8=BBB DATA
MapAll9=BBB DATA
CHAPT E R 4
25
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 carrier
entries, 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.
Of course, these configuration levels correspond with the most important scenarios. The passwords are saved in
the ip.cfg in encrypted form:
PwdCarrier=<crypt>
PwdAdmin=<crypt>
PwdUser=<crypt>
Example:
The user interface is divided into the following main sections:
[httpd]
PwdUser=k24X0sdc.uMcM
PwdAdmin=k2UMj19qtovzI
PwdCarrier=k2jryo6Xd5vN6
Never copy these entries from one system to another, as the encryption is unique for
each system.
Table 4.5 HTTP User Interface: Sections
Section Description
User Data Here you can change the user passwords and the language for the HTTP in-
terface.
i i
CHAPT E R 4
26
All of the user interfaces pages contain Help buttons and links to the online help, which provides a detailed de-
scription of all of the individual configuration settings.
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 teles and 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.
System Settings IP Settings: Settings for the Ethernet interfaces and related services.
ISDN Settings:Settings for the VoIPBOX BRIs BRI interfaces.
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.
Table 4.6 FTP Security Entries
FTP Security
FtpdPort=<port>
Defines the FTP access port (default 21).
RemotePassword=<password>
Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.11.4 for instructions
on how to enter an encrypted password in the pabx.cfg. If you do not define a password, access to the
system via GATE Manager occurs without a password, and FTP access occurs with the default password
tcs-ag.
Table 4.5 HTTP User Interface: Sections (continued)
Section Description
CHAPT E R 4
27
The following commands can be carried out via FTP access:
4 . 1 1 . 4 S E T T I N G A PA S S WO R D F O R R E MO T E A C C E S S
The following entry ensures the security of your remote access. Use the mkpwd.exe tool to generate the pass-
word. You will find it on the enclosed CD in the directory pwd.
Start the program in a command window with the entry mkpwd <password>. The output shows the encrypted
password. 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 system
can 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.
Table 4.7 FTP Commands
Command Function
SITE xgboot Boots the entire system.
SITE xgact Activates the configuration.
SITE xgact 1-19 Activates the Night section 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.
RemotePassword=<crypt>
CHAPT E R 5
28
5 CONF I GURAT I ON F I L ES
This chapter describes the basic setup and the most commonly used entries for the configuration files. Configura-
tion of VoIPBOX BRIes 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 the
files are not on the system. You can configure the system using Quickstart, GATE Manager or via FTP (user teles,
password tcs-ag). If you use the HTTP user interface 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 the
passwords!
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. Configuration
files must end with an empty line.
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 are in these files:
Table 5.8 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 as
possible consequential damage. All changes are made at own risk. TELES is not liable
for any possible damage out of or in relation to such changes. Please thoroughly
check any changes you or a third party have made to your configuration.
Table 5.9 Required Configuration File Sections
Section File Function
[System] pabx.cfg
route.cfg
ip.cfg
This section contains the systems basic settings.
i i
C O N F I G U R A T I O N F I L E I P . C F G
CHAPT E R 5
29
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, these
settings are entered once and then left unchanged.
This file contains the following sections, which must appear in the order given:
[Night<num>]
EXAMPLE:
[Night1]
[Night2]
pabx.cfg
route.cfg
This section contains time dependent entries that only apply for
limited times.
[emac0] ip.cfg This section contains the IP configuration for the first Ethernet in-
terface.
Table 5.10 Sections in the ip.cfg File
Section Function
[System] (required) This section contains entries that define the default gateway and/or special
routing entries.
[emac0] (required)
[emac1] (optional)
The Ethernet Media Access Controller section(s) define the physical Ethernet
interface(s).
[nat] (optional) This section includes settings for Network Address Translation.
[bridge0] (optional) These section(s) contain settings for the second Ethernet controller in bridge
mode.
[pppoe<x>] (optional) These sections contain settings for direct connection between the system
and the DSLAM when the PPPoE protocol is used. <x> can be 0 or 1.
[firewall] (optional) This section contains settings for activating the systems firewall.
[altqd] (optional)
This section enables prioritization of VoIP packets in the VoIPBOX BRI
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 parameters
for the DHCP subnet.
[vlan<x>] (optional) These section(s) contain settings for the virtual networks. <x> can be any-
thing from 0 to 9.
Table 5.9 Required Configuration File Sections (continued)
Section File Function
CHAPT E R 5
30
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=<ip addr>
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=<target range> -netmask <ip mask> <ip gateway>
Example:
If only certain routes apply, leave the line DefaultGw empty.
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=<ip addr>/<netmask>
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 B R I D GE 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 <interface-x> add <interface-y> up
[System]
DefaultGw=192.168.1.254
[System]
DefaultGw=192.168.1.254
Route=10.0.0.0 -netmask 255.0.0.0 192.168.1.1
IpAddress=192.168.1.2/24
CHAPT E R 5
31
Activating another Ethernet interface in this way is useful, for example, when the Ethernet switch does not have
any more ports available for connection of the system. You can simply unplug a cable and plug it into the systems
second Ethernet interface.
Example:
5 . 1 . 4 N AT 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:
[bridge0]
BrConfig=add emac0 add emac1 up
Table 5.11 NAT Configuration
map=<interface> <local network address/mask> -> <public network address/mask> <optional
entries>
This parameter maps the IP address in the local network to the IP address in the public network.
<interface> Defines the translated interface or protocol:
emac1 The systems second Ethernet interface
pppoe0 Protocol used for DSL connections
xppp<0> Protocol used for ISDN dial-up connections
<local network
address/mask>
The IP address is entered in decimal notation, followed by a slash (/) and the netmask
in bit notation. The entire local network range is configured.
<public net-
work address/
mask>
Defines the public network range, with network address and mask (usually exactly one
address), into which the local IP addresses are to be translated. The IP address is entered
in decimal notation, followed by a slash (/) and the netmask in bit notation.
<optional en-
tries>
Special rules can be defined for some services or protocols. The system can serve as a
proxy for FTP:
proxy port ftp ftp/tcp
Special ports for the public address(es) can be assigned for the protocols TCP and UDP.
The range is defined by the start and end ports:
portmap tcp/udp <start port>:<end port>
If no optional entry is defined, all other addresses will be translated without special
rules.
rdr=<interface> <public network address/mask> port <port> -> <local network address/mask>
port <port_number> <protocol>
This parameter redirects packets from one port and IP address to another.
CHAPT E R 5
32
Example: The following NAT settings are for a system in which PPPoE (DSL) is used toward the Internet.
The local network range 192.168.1.0 Class C is translated with the following rules:
The proxy mode is used for FTP.
All other TCP and UDP packets are mapped to the external ports 40000 to 60000.
There are no special rules for any other services.
Incoming requests to port 80 and 443 in the public IP address 192.168.1.100 are redi-
rected to ports 80 and 443 in the local IP address 192.168.1.100.
5 . 1 . 5 P P P O E C O N F I G U R A T I O N
The protocol Point-to-Point over Ethernet is used for DSL communication with the DSLAM. That means the system
can connect directly with the carrier network and terminate VoIP traffic directly.
All necessary information for setup of the PPPoE connection is defined in the [pppoe<x>] section. That means
username, password and authentication protocol are set here. The Ethernet interface is emac1 and the gateway
can also be defined. The parameter PppoeIf defines the physical Ethernet interface used (always emac1). The
settings are entered as follows:
[pppoe<x>]
PppoeIf=emac1
User=<user>
<interface> Defines the translated interface or protocol:
emac1 The systems second Ethernet interface
pppoe0 Protocol used for DSL connections
ppp<0> Protocol used for ISDN dial-up connections
<public net-
work address/
mask>
Defines the public network range, with network address and mask (usually exactly one
address), into which the local IP addresses are to be translated. The IP address is entered
in decimal notation, followed by a slash (/) and the netmask in bit notation.
<port> Defines the port number.
<local network
address/mask>
The IP address is entered in decimal notation, followed by a slash (/) and the netmask
in bit notation. The entire local network range is configured.
<protocol> Defines the protocol. tcp and udp are possible.
[nat]
map=emac1 192.168.1.0/24 -> 0/32 proxy port ftp ftp/tcp
map=emac1 192.168.1.0/24 -> 0/32 portmap tcp/udp 40000:60000
map=emac1 192.168.1.0/24 -> 0/32
rdr=emac1 0/0 port 80 -> 192.168.1.100 port 80 tcp
rdr=emac1 0/0 port 443 -> 192.168.1.100 port 443 tcp
Table 5.11 NAT Configuration (continued)
CHAPT E R 5
33
Pwd=<pwd>
AuthProto=<pap|chap>
Route=<ip_gw> (optional)
Bear in mind that configuration of the firewall, the NAT module and prioritization of the VoIP packets must be con-
sidered when routing voice and data through the DSL line.
Example: The following entry will create the interface pppoe0, with the username user and the pass-
word pwd. The PAP authentication protocol is used. The default route occurs via DSL:
5 . 1 . 6 F I R E WA L L S E T T I N G S
The firewall settings provide options for limiting or denying access to and from the system. If you do not configure
this section, the firewall is inactive and access is unlimited.
WARNING: Make sure you configure the firewall rules carefully. The rules are processed from top to bottom. If
you use the option quick, you will break the sequence. We recomend that you put the most restrictive rule at the
end of the configuration.
Table 5.12 Settings in the [pppoe<x>] Section of the ip.cfg
[pppoe<x>]
PppoeIf=<interface>
Enter the Ethernet interface used for the DSL connection (usually emac1).
User=<username>
Enter the username used for DSL access.
Pwd=<password>
Enter the password used for DSL access.
AuthProto=<protocol>
Enter chap or pap for the protocol used for authentication.
Route=<ip-addr> (optional)
Enter the target IP address range, e.g. 0.0.0.0 (default route). All packets that are not defined for the local
network will be sent through this interface. In this case, the parameter DefaultGW in the System section
(Chapter 5.1.1 ) must remain empty. Only network ranges can be routed. The syntax in this case is
Route=<target range> -netmask <ip mask>. If several different network ranges are used, you
must enter the Route parameter for each range.
[pppoe0]
PppoeIf=emac1
User=user
Pwd=pwd
AuthProto=pap
Route=0.0.0.0
CHAPT E R 5
34
Example: In the following example, only port 4445 allows incoming connections from the IP address
192.168.1.10. All others will be blocked.
[firewall]
fw=pass in quick on emac0 proto tcp from 192.168.1.10/32 to any port
eq 4445 flags S keepstate keep frags
fw=block in log quick on emac0 all
Table 5.13 Settings in the [firewall] Section of the ip.cfg
[firewall]
fw=<mode> <direction> <list>
<mode> Two modes are possible for permitting or denying access::
pass permits access
block denies access
<direction> Possible directions are in and out:
in external to internal
out internal to external
<list> All other entries specify the other settings for the corresponding firewall rules and are
optional. The order in the line is as listed below:
log
Records non-matching packets.
quick
Allows short-cut rules in order to speed up the filter or override later rules. If a packet matches a filter
rule that is marked as quick, this rule will be the last rule checked, allowing a short-circuit path to avoid
processing later rules for this packet. If this option is missing, the rule is taken to be a "fall-through rule,
meaning that the result of the match (block/pass) is saved and that processing will continue to see if there
are any more matches.
on <interface>
The firewall rule is used only for the defined interface (e.g. emac0, pppoe0).
from <networkaddress/mask>
to <networkaddress/mask>
from defines the source IP-address range for incoming packets. to defines the target IP-address range for
outgoing packets. The IP address appears in decimal notation, followed by a slash (/) and the netmask in
bit notation. any stands for all IP addresses (e.g.: to any).
NOTE: If you use the rule pass in/out in combination with the option from <ip> to <ip>, you
must specify a protocol number with proto and a port number. If you not specify the port, the system
may not be reachable. EXAMPLE:
fw=pass in quick on pppoe0 proto tcp from any to any port eq 4445
CHAPT E R 5
35
Example:
5 . 1 . 7 B A N D WI D T H C O N T R O L
In many implementation scenarios, the VoIPBOX BRI in router mode (e.g. as DSL router) sends voice and data traffic
through a connection with limited bandwidth. This can lead to lost voice packets that arrive too late to be used in
the voice stream. To avoid lost packets, this QOS setting prioritizes packet transmission. You must set the priority
for voice signaling and for the voice packets. That means you must prioritize SIP/H.323, RTP and RTCP. You will
find the ports used in Table 5.22, in the following entries:
proto <protocol>
defines the protocol, for which the rule is valid (e.g.: proto tcp, proto udp, proto icmp).
port eq <num>
<num> defines the port as number (e.g.: port eq 4445).
keep state
Ensures that the firewall checks packets from the beginning to the end of a session. This is necessary, as the
firewall does not know when a session begins or ends.
flags S
Only syn. packets are accepted and recorded in the state table. In conjunction with keep state, packets from
sessions that have been inactive will also be routed. The advantage of this entry is that random packets will
not be accepted.
keep frags
Fragmented packets are also routed.
[firewall]
; loopback
fw=pass in quick on emac0 all
fw=pass out quick on emac0 all
; traffic to outgoing
fw=pass out quick on pppoe0 proto tcp all flags S keep state keep frags
fw=pass out quick on pppoe0 proto udp all keep state keep frags
fw=pass out quick on pppoe0 proto icmp all keep state keep frags
; incoming traffic
fw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 21 flags S keep state keep frags
fw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state
; icmp traffic
fw=pass in quick on pppoe0 proto icmp all keep state
; other will be blocked
fw=block in log quick on pppoe0 all
fw=block out log quick on pppoe0 all
Table 5.13 Settings in the [firewall] Section of the ip.cfg (continued)
[firewall]
fw=<mode> <direction> <list>
CHAPT E R 5
36
H225Port
SipPort
VoipRtp Port
VoipRtpPortSpacing
Different ports can be used for RTP and RTCP, depending on the configuration.
The parameter VoipRtpPort shows the first RTP port used. The corresponding RTCP port is the next one up.
The parameter VoipRtpPortSpacing shows the next RTP port (RTP port + port spacing).
Example: In the following example, prioritization is set for an eight-channel VoIP connection. The SIP sig-
naling port 5060 and the RTP/RTCP ports 29000 to 29015 are prioritized at level 7. All other
services are set at level 0:
Table 5.14 Settings in the [altqd] Section of the ip.cfg
interface <interface> bandwidth <bw> priq
Defines the interface for which the rule applies.
<interface> Sets the interface for which prioritization apples (e.e. pppoe0).
<bw> Sets the bandwidth that is available on the interface in Kbit/s (e.g. 256K).
priq Priority qeueing. A higher priority class is always served first.
class priq <interface> <class> root priority <prio>
Defines the priority of the filter entries.
<class> Two types can be set:
realtime_class (VoIP packets)
regular_class (data packets)
<prio> Enter a value between 0 and 15. The higher the value (e.g. 15), the higher the priority.
filter <interface> <class> <values>
Defines the individual rules.
<values> The individual values are divided into the following entries. A 0 can be entered as a wild-
card, in which case all values are possible:
<dest_addr> (can be followed by netmask <mask>)
<dest_port>
<src_addr> (can be followed by netmask <mask>)
<src_port>
<protocol tos value>:
6 for TCP
17 for UDP
CHAPT E R 5
37
5 . 1 . 8 D H C P S E R V E R S E T T I N G S
The DHCP (Dynamic Host Configuration Protocol) server provides a mechanism for allocation of IP addresses to
client hosts. The section [dhcpd] contains a list of parameters and settings for the DHCP server in the system. It
is divided into global settings for the server and parameters for the DHCP subnet.
[altqd]
interface pppoe0 bandwidth 256K priq
class priq pppoe0 realtime_class root priority 7
filter pppoe0 realtime_class 0 5060 0 0 0
....
class priq pppoe0 regular_class root priority 0 default
Table 5.15 Settings in the [dhcpd] Section of the ip.cfg
; Global dhcp parameters
allow unknown-clients;
All DHCP queries are accepted and the configured settings are transmitted to the clients.
ddns-update-style none;
Deactivates dynamic update of the domain name system as per RFC 2136.
; Parameters for the Subnet
subnet <network address> netmask <mask for network range> {
<list>
}
In <list> you can enter any of the following specific network settings activated by the DHCP server. Each op-
tion must begin in a new line and end with a semicolon (;).
range <start IP address> <end IP address>;
The DHCP network range is defined by the first and last address in the range. Client assignment begins with
the last address.
option broadcast-address <IP address>;
Defines the broadcast address for the clients in the subnet..
option domain-name "<string>";
Defines the domain name used in the network.
CHAPT E R 5
38
Example:
5 . 1 . 9 P P P C O N F I G U R A T I O N F O R I S D N D I A L - U P
The point-to-point protocol is used for dial-up connection via ISDN lines. That means the system can set up an In-
ternet connection, which can be used for all local users or to transmit VoIP calls via ISDN dial-up. Bear in mind that
you must configure the firewall and NAT options accordingly.
option domain-name-servers <IP address>;
Defines the DNS-server address to be assigned (as per RFC 1035)
All of the following optional entries defining server addresses are also transmitted as per RFC 1035. Separate
multiple addresses per server with a comma:
<IP address>, <IP address>;
(this also applies for all other optional entries with IP addresses).
option netbios-name-servers <IP address>
Defines the WINS-server address to be assigned.
option ntp-servers <ip address>;
Defines the NTP-server address to be assigned.
option time-servers <ip address>;
Defines the time-server address to be assigned (RFC 868).
option routers <IP address>;
Defines the router address to be assigned.
option subnet-mask <net mask>;
Defines the netmask to be assigned (as per RFC 950).
option tftp-server-name "<link>";
Defines the TFTP server name (option 66), as per RFC 2132.
EXAMPLE: option tftp-server-name "http://192.168.0.9";
[dhcpd]
; Parameter for the Subnet
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.3 192.168.1.20;
option broadcast-address 192.168.1.255;
option domain-name "company.de";
option domain-name-servers 192.168.1.100;
option routers 192.168.1.2;
option subnet-mask 255.255.255.0;
}
Table 5.15 Settings in the [dhcpd] Section of the ip.cfg (continued)
CHAPT E R 5
39
The advantages of VoIP over ISDN can be seen especially in corporate implementation. For example, it is useful
when a very high number of connections occurs between subsidiaries and one subsidiary does not have a broad-
band Internet connection. An ISDN B-channel can be connected to the Internet and up to six voice calls can occur
simultaniously over one ISDN line. All necessary information for setup of the PPP connection is defined in the sec-
tion [xppp<num>].
The settings are entered as follows:
Example:
Table 5.16 Settings in the [xppp] Section of the ip.cfg
[xppp<num>]
Dad=<num>
Enter the dial-up number.
User=<username>
Enter a username.
Pwd=<password>
Enter a password.
Route=<ip-addr>
Enter the target IP address range, e.g. 0.0.0.0 (default route).
AuthProto=<protocol>
Enter chap (default) or pap for the protocol used for authentication.
IdleTO=<sec>
Enter the number of seconds without traffic before the interface tears down the connection.
MTU=<int>
Maximum Transfer Unit. We recommend the following default values:
1500 for ISDN dial-up.
Rfc1662=<val>
Framing to be use:
0 for ISDN.
[xppp0]
Dad=12345
User=user
Pwd=pwd
Route=0.0.0.0
AuthProto=chap
IdleTO=60
MTU=1500
Rfc1662=0
CHAPT E R 5
40
5 . 1 . 1 0 V L A N C O N F I G U R A T I O N
A VLAN (Virtual Local Area Network) is a virtual LAN within a physical network. Each VLAN is assigned a unique
number (VLAN ID) and defined in the [vlan<x>] section with
Tag: value between 1 and 4095
Priority: value between 0 and 7 (0 is lowest and 7 is the highest priority)
[vlan0]
IfConfig=vlan <tag>,<priority> vlanif <interface>
Example: The following entry will create the interface vlan1, with VLAN tag 10 and priority 7, on the Ether-
net interface emac0. Following this configuration, IP addresses (and/or other protocols) can be
assigned to the vlan1 interface:
5 . 1 . 1 1 E X A MP L E S
5 . 1 . 1 1 . 1 D E F A U L T C O N F I G U R A T I O N
In the following example, the systems IP address is 192.168.1.1, the netmask is 255.255.255.0, and the standard
gateway is 192.168.1.254:
5 . 1 . 1 1 . 2 A C T I V E E T H E R N E T B R I D GE
In the following example a two-port Ethernet bridge is configured. The systems IP address is 192.168.1.1, the net-
mask is 255.255.255.0, and the standard gateway is 192.168.1.254,
The emac1 interface is active and both Ethernet interfaces are set to bridge mode in the [bridge0] section:
[vlan1]
IfConfig=vlan 10,7 vlanif emac0
IpAddress=192.168.199.1
[System]
DefaultGw=192.168.1.254
[emac0]
IpAddress=192.168.1.1/24
[System]
DefaultGw=192.168.1.254
[emac0]
IpAddress=192.168.1.1/24
[emac1]
IpAddress=up
[bridge0]
BrConfig=add emac0 add emac1 up
CHAPT E R 5
41
5 . 1 . 1 1 . 3 I N T E G R A T E D D S L - R O U T E R S C E N A R I O F O R VO I P TR A F F I C WI T H
A N A C T I V E D H C P S E R V E R A N D F I R E WA L L
In the following example, the system is connected to the local IP network through emac0. The DSL modem is con-
nected to the emac1 interface, which enables the system to connect directly to the carrier network without an ad-
ditional router when the connection is used only for VoIP data. A DHCP server is used for dynamic IP-address
allocation:
[System]
[emac0]
IpAddress=192.168.0.2/24
[emac1]
IpAddress=up
[pppoe0]
PppoeIf=emac1
User=usertelekom
Pwd=pwd
AuthProto=chap
Route=default
[nat]
map=pppoe0 192.168.0.0/24 -> 0/32 proxy port ftp ftp/tcp
map=pppoe0 192.168.0.0/24 -> 0/32 portmap tcp/udp 40000:60000
map=pppoe0 192.168.0.0/24 -> 0/32
[firewall]
; loopback
; traffic to outgoing
fw=pass out quick on pppoe0 proto tcp all flags S keep state keep frags
fw=pass out quick on pppoe0 proto udp all keep state keep frags
fw=pass out quick on pppoe0 proto icmp all keep state keep frags
; incoming traffic
fw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state
; icmp traffic
fw=pass in quick on pppoe0 proto icmp all keep state
; other will be blocked
fw=block in log quick on pppoe0 all
fw=block out log quick on pppoe0 all
[dhcpd]
; Parameter for the Subnet
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.3 192.168.1.20;
option broadcast-address 192.168.1.255;
option domain-name "company.de";
option domain-name-servers 192.168.1.100;
option routers 192.168.1.2;
option subnet-mask 255.255.255.0;
C O N F I G U R A T I O N F I L E P A B X . C F G
CHAPT E R 5
42
5 . 1 . 1 1 . 4 V L A N S C E N A R I O
In the following example, the system is connected to the IP backbone through emac0. One Computer is connected
to the emac1 interface. You can separate voice and data traffic with two different VLANs (vlan0 with tag 10 for
voice, vlan1 with tag 11 for data). All traffic coming from emac1 will be sent to vlan1. Voice and data will not be
mixed:
5 . 2 C O N F I G U R A T I O N F I L E P A B X . C F G
The pabx.cfg is divided into the [System] section and the optional [Night<num>], [Mail] and
[Snmpd] sections.
5 . 2 . 1 S Y S T E M S E T T I N G S
The [System] section is divided into several categories to ensure clarity:
Hardware
Bypass relay
Log files
Night configuration
Controllers
Subscribers
Global Settings
5 . 2 . 1 . 1 B Y P A S S R E L A Y
The entry in this category is responsible for the bypass functionality of the BRI ports relay when the system is on.
When the system is off, BRI port 1 is connected to BRI port 3, and BRI port 2 is connected to BRI port 4. This means
there is a transparent connection between the PBX (or the telephones) and the PSTN. When the system is on, all
routing algorithms are active.
Bypass=ON/OFF
ON: BRI relay is on (system controls both BRI ports).
[System]
[emac0]
IpAddress=192.168.1.12/16
[emac1]
IpAddress=up
[vlan0]
IpAddress=10.0.1.2/24
[vlan1]
IpAddress=172.16.4.5/16
[bridge0]
BrConfig=add vlan1 add emac1 up
CHAPT E R 5
43
OFF: BRI relay is off (both BRI ports are connected to each other, regardless of whether or not the system is run-
ning).
5 . 2 . 1 . 2 L O G F I L E S
CDRs, unconnected calls, system events, trace output and statistics can be saved into files.
The following entries are necessary to generate log files:
You can define how the log files are to be divided. There are two possiblities 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.
This parameter should always be set to ON.
Table 5.17 pabx.cfg: Log File Entries
Entry Description
ActionLog=/boot/protocol.log System events
Log=/boot/cdr.log CDR entries
RRufLog=/boot/failed.log Unconnected calls
TraceLog=/boot/trace.log System trace
The available internal memory is approximately 8 MB. Make sure you monitor the
available memory.
Table 5.18 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.
i i
i i
CHAPT E R 5
44
Example 1 In the following entry, the file cdr.log is renamed every day. Up to 35 CDR files will be saved
on the system.
Example 2 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 3 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.
<saved> Refers to the frequency with which the file is saved. The following options 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.
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 of 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.
Log=/boot/cdr.log daily - 35
RrufLog=/boot/failed.log weekly - 10
ActionLog=/boot/protocol.log - 1000 5
Table 5.18 pabx.cfg: Log Parameters (continued)
Log=/boot/<file> <saved> <size> <count>
i i
CHAPT E R 5
45
5 . 2 . 1 . 3 N I G H T C O N F I G U R A T I O N
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:
Example: The configuration section is activated Fridays, Wednesdays and Mondays at noon unless the day
in question is a holiday:
Night2=12:00 00101010
The configuration section switches back to the default configuration (System section) every day
at 8:00 p.m:
NightResetTime=20:00 11111111
The configuration section is activated on November 5, December 24, and at noon on Mondays:
Night1=12:00 10000010
Holiday=05.11.
Holiday=24.12.
Please remember to keep track of how much memory is available on the system.
Table 5.19 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 configuration 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 day-
mask appears in the following order: HoSaFrThWeTuMoSu.
Any defined Night sections must be set in the files pabx.cfg and route.cfg. If
there are no changes in these sections, you must copy them from the System section.
The complete Subscriber section must appear in the Night section of the
pabx.cfg (see Chapter 5.2.4 on page 5-53). The active route(s) (MapAll, Restrict
and Redirect entries) must appear in the Night section of the route.cfg (see
Chapter 5.3 on page 5-54).
i i
i i
CHAPT E R 5
46
5 . 2 . 1 . 4 C O N T R O L L E R S
This category defines the parameters that apply to the ports.
The individual ports are defined with the following parameters:
Table 5.20 pabx.cfg: Controller Parameters
Controller<port>=<bus> <type> <mode> <line_type> UNIT: VALUE:
<port> Defines the running (physical) port number.
<bus> Defines the configured (virtual) port number. In the default configuration, BRI TE ports
are 9 and BRI NT ports are 10. VoIP ports are 40.
<type> Defines the connection type:
TE external (Terminal Endpoint)
NT internal (Network Termination)
VOIP VoIP module
DTMF virtual controller for activating DTMF tone recognition
<mode> Defines the protocol for BRI lines:
DSS1
<line_type> Defines Point-to-Multipoint or Point-to-Point mode:
PMP Point-to-Multipoint
PP Point-to-Point
UNIT: (Optional) Defines the currency for the charges (default EUR). Special charge generation
is possilbe for:
France UNIT:&F
Spain UNIT:&SP
Portugal UNIT:&P
Greece UNIT:&G
Switzerland
UNIT:&CH
Netherlands
UNIT:&NL
Italy UNIT:&I
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
VALUE: (Optional) Defines the charges that accumulate for each unit (default 12).
CHAPT E R 5
47
Ports set to the same type can have the same bus number. In this case they will form a trunk group. If you change
this parameter in the configuration, you must restart the system.
Example:
5 . 2 . 1 . 5 S U B S C R I B E R S
Features for each port can be defined using this entry. Changes become active following a restart:
Controller00=9 TE DSS1 PMP
Controller01=9 TE DSS1 PMP
Controller02=10 NT DSS1 PMP
Controller03=10 NT DSS1 PMP
Controller04=40 VOIP
Table 5.21 pabx.cfg: Subscriber Parameters
Subscriber<port>=<list>
<port> Defines the running (physical) port number.
The <list> variable may contain one or more of the following keywords:
DEFAULT The standard configuration will be used.
TRANSPARENT ROUTER Only the number is sent as caller ID (without the virtual port address).
ALARM Activates the monitoring mode for the respective port. If a relevant error oc-
curs at the port, a remote call is placed to the number defined in
RemoteCallBack.
SWITCH Changes internal port handling. In the default configuration, the VoIP con-
troller is set to NT. You can use this parameter to change it from NT to TE.
CHMAX[x] Defines the number of VoIP channels (8) or DTMF channels. A maximum of
two concurrent channels are possible for DTMF recognition if the callback
platform is used.
DTMF[<sec>,/<dir>/
<file>]
Please refer to Chapter 11.1.1 .
CHAPT E R 5
48
5 . 2 . 1 . 6 G L O B A L S E T T I N G S
This category contains the following system parameters:
Subscriber00 = TRANSPARENT ROUTER ALARM
Subscriber04 = TRANSPARENT ROUTER SWITCH CHMAX[8] ALARM
Table 5.22 pabx.cfg: IP Configuration System Parameters
System Parameters
VoipGlobalMaxChan=<count>
Max. number of channels for the entire system.
VoipRtpPort=<port>
Defines the starting UDP port used to transmit RTP packets (default 29000).
VoipRtpPortSpacing=<count>
Defines the space between the ports used for individual RTP streams (default 2).
H225Port=<port>
Endpoint-to-endpoint port (default 1720).
SipPort=<port>
SIP signaling port (default 5060).
VoipMaximumBandwidth=<int>
Defines an upper limit for available bandwidth for the VoIP profiles to be configured (see
VoipBandwidthRestriction in Table 12.97) if traffic shaping is active for the corresponding VoIP
profile. Individual codecs are assigned the following values:
g711a, f711u, trp: 8
g72632, t38: 4
g72624 3
g72616, gsm 2
Other 1
You must define the list of codecs to be used in the VoIP profiles, whereby the codec with the highest priority
must be defined first. Calls will be set up using the codec with the highest priority as long as the sum of the
values for individual calls remains lower than defined here. If the sum is greater, the next call will be set up
with, and existing calls will be switched to, a higher compression rate. Bear in mind that the VoIP peer must
support this feature.
VoipStrictRfc3261=<mode>
If yes is set, the SIP transaction/dialog matching will occur strictly as per RFC3261. You must disable this
feature for peers that use RFC2543 (from and to name). Default is yes.
CHAPT E R 5
49
StunServerAddress=<ip addr>
When this parameter is active, the VoIPBOX BRI looks for a (NAT) firewall in the network and figures out how
to bypass it without requiring changes. All ports for signaling, RTP and RTCP are checked. The parameter
VoipGlobalMaxChan defines the number of ports for RTP and RTCP.
NOTE: This is not a solution for all firewall types.
StunServerPollInterval=<sec>
Interval (in seconds) for the stun request at each port (default 600).
Radius=<mode>
On (default) activates the Radius service. If you change Off to On, you must restart the system.
RadiusAuthPort=<num>
Port used for Radius authentication (default 1812).
RadiusAcctPort=<num>
Port used for Radius accounting (default 1813).
NameServer=<ip addr>
IP-address configuration for the DNS server. Enter your network or ISPs DNS server. If you dont 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.
Timezone=<continent/city>
Defines the time difference between the VoIPBOX BRIs time zone and time zone 0 (Greenwich Mean Time).
Enter the continent and a large city (usually the capital) in the time zone.
NtpServer=<ip addr>
Sets the IP address at which the VoIPBOX BRIs SNTP server queries the standard time. The query occurs every
four hours.
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:
Subscriber=...TIME
MoipPort=<port>
Defines the GATE Manager access port (default 4445).
FtpdPort=<port>
Defines the FTP access port (default 21).
TelnetdPort=<port>
Defines the TELNET access port (default 23).
Table 5.22 pabx.cfg: IP Configuration System Parameters (continued)
System Parameters
CHAPT E R 5
50
Example:
TftpdPort=<port>
Defines the TFTP access port (default 69).
Ftpd=<mode>
Activates (on) or deactivates (off) FTP access. Default on.
Telnetd=<mode>
Activates (on) or deactivates (off) TELNET access. Default on.
Tftpd=<mode>
Activates (on) or deactivates (off) FTP access. Default off.
RemotePassword=<password>
Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.11.4 for instructions
on how to enter an encrypted password in the pabx.cfg. If you do not define a password, access to the
system via GATE Manager occurs without a password, and FTP access occurs with the default password
tcs-ag.
DialTone=<country>
If the system is used in a corporate settings and attached through a PBX to the PSTN, it may be necessary to
generate the carriers dial tone. It depends on whether the system sends the dialed digits to the PSTN or
whether it waits for a routing entry to take the call.
The following values can be entered:
GE
DE
IR
UK
US
FR
IT
VoipGlobalMaxChan=8
H225Port=1720
SipPort=5060
VoipRtpPort=29000
VoipRtpPortSpacing=2
StunServerAddress=172.16.0.1
StunServerPollInterval=600
NameServer=192.168.0.254
Timezone=Europe/Berlin
NtpServer=192.168.0.254
DialTone=GE
Table 5.22 pabx.cfg: IP Configuration System Parameters (continued)
System Parameters
CHAPT E R 5
51
5 . 2 . 2 S MT P - C L I E N T C O N F I G U R A T I O N
The following entries in the pabx.cfgs [Mail] section are used to send e-mail messages from the
VoIPBOX BRI. The connection to the SMTP server can be used to send CDR files or alarm messages.
The following features are possible:
Sending CDRs via e-mail
Sending alarm messages via e-mail
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!
Therefore it is important to set the system time with an NTP server.
If the system is connected via BRI, a clock may come from the network connected to
the corresponding port. Enter TIME in the pabx.cfgs Subscriber line for the BRI
port to take the time from the port.
You must restart the system after making changes to activate the settings.
SmtpServer=<ip addr>
In <ip addr>, enter the IP address of the destination SMTP server that is to receive the e-mail messages.
MailUserIn=<username>
Enter a username for incoming e-mail authentication.
MailUserOut=<username>
Enter a username for outgoing e-mail authentication.
MailPwdIn=<password>
Enter a password for incoming e-mail authentication.
MailPwdOut=<password>
Enter a password for outgoing e-mail authentication.
MailAuthEncr=<type>
Enter an encryption method for e-mail authentication (default base64).
MailRcpt=<domain>
In <domain>, enter the destination domain, the destination address and an @ sign. If the destination ad-
dress is already complete (with an @ sign), <domain> is not added.
i i
i i
CHAPT E R 5
52
MailFrom=<domain>
In <domain>, enter the source domain, the source address and an @ sign. If the source address is already
complete (with an @ sign), <domain> is not added.
MailRcvMax=<count>
Maximum number of incoming e-mails queued for transmission via SMS or USSD.
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).
MaxMailsToHost=<count>
Maximum number of e-mail messages sent to the LCR simultaneously.
MailToHostDelay=<count>
Number of seconds until an e-mail message is sent to the LCR (this timer runs separately for each
MaxMailsToHost message).
MailToHostRetries=<count>
Number of retries when SMS transmission is not successful. When the limit entered is reached, an error mes-
sage is sent to the e-mail sender (default 3).
MailSendRetries=<count>
Number of times an attempt is made to send an e-mail.
MailMaxIncomingClients=<count>
Defines the maximum number of clients that can access the system simultaneously. If 0 is entered, the SMTP
port (25) will be blocked for incoming sessions. Default 5.
MailTcpRcvTimeout=<sec>
Defines the number of seconds after which a session will be terminated following a possible receiving error
in the data stream. Default 0 (immediately).
MailTcpSndTimeout=<sec>
Defines the number of seconds after which a session will be terminated following a possible transmission
error in the data stream. Default 0 (immediately).
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.
MailPropPort=<num>
Enter the port number for a TELES proprietary mail protocol.
CHAPT E R 5
53
Example:
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 systems name appears in the subject box. The text box contains the
alarm message.
The following entry in the configuration file activates this function:
5 . 2 . 3 S N MP S E T T I N G S
The Simple Network Management Protocol facilitates network management and monitoring of VoIPBOX BRI net-
work devices and their functions. For a detailed description of SNMP configuration, please refer to
Chapter 13.4 .
5 . 2 . 4 T I ME - C O N T R O L L E D C O N F I G U R A T I O N S E T T I N G S
The [Night<num>] section is reserved for prospective time-controlled configuration changes. In the
pabx.cfg file, the Night sections contain all of the systems Subscriber entries. Simply copy all
Subscriber lines into the Night Section without making any changes.
[Mail]
SmtpServer=172.16.0.10
MailRcpt=teles.de
MailFrom=172.16.0.100
MailRcvMax=500
MailRcptMax=100
MaxMailsToHost=2
MailToHostDelay=3000
MailToHostRetries=10
MailSendRetries=10
MailAllowedPeers=172.16.0.10
...
ActionLog=/data/protocol.log daily 1000 5 @<e-mail account>
...
You must restart the system after making changes to activate the settings.
i i
C O N F I G U R A T I O N F I L E R O U T E . C F G
CHAPT E R 5
54
5 . 3 C O N F I G U R A T I O N F I L E R O U T E . C F G
The systems 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>]
5 . 3 . 1 E N T R I E S I N T H E S E C T I O N S [ S Y S T E M] A N D [ N I G H T < N U M> ]
The sections [System] and [Night<num>] contain the following entries.
5 . 3 . 1 . 1 MA P P I N G
Mapping entries begin with the keyword MapAll.
Example: In the following example, all international calls are sent to the VoIP carrier (40) with the profile
name DF. All national calls are sent to the BRI controller with the number 9:
Table 5.23 route.cfg: Map Parameters
MapAll<direct>=<num> <mode>
<direct> Defines the prefix or telephone number for which the entry applies.
<num> Defines the following in the order given:
Destination ports controller number
Optional VoIP profile name followed by 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 digit.
<mode> VOICE Applies for calls with the service indicator voice (default).
DATA Applies for calls with the service indicator data.
MapAll00=40DF:00
MapAll0=90
CHAPT E R 5
55
5 . 3 . 1 . 2 R E S T R I C T
This entry is for controller-specific routing entries. These entries apply only for a single controller and can be set for
an OAD base number or an MSN:
Example: In the following example, all calls coming from BRI controller 9 (PSTN)are sent to BRI controller
10 (PBX) without regard to the routing file:
Table 5.24 route.cfg: Restrict Parameters
Restrict<ns>=<num> <sin>
<ns> Defines the virtual controller number plus an optional base number or a specific calling
number. The special symbol ? may be used as a wildcard to represent any digit.
<pl> Stands for a virtual placeholder used for the mapping entry that routes calls for the the
Restrict command.
<sin> The service indicator variable sin restricts 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 Videotext (new standard)
16 Video telephone
Restrict9=pl
MapAllpl=10
CHAPT E R 5
56
5 . 3 . 1 . 3 R E D I R E C T
This entry facilitates alternative routing when the first destination cannot be reached or is busy. A placeholder ap-
pears to the right of the equal sign. The routing entry (MapAll) can be defined for the redirect using the place-
holder entered:
Table 5.25 route.cfg: Redirect Parameters
Redirect<type><num>=<redirect> <sin> <time>
<type> Enter 2, 3 or 5 to set the following types:
2 call forwarding no answer
3 call forwarding when busy
5 call forwarding when busy and no answer
<num> Defines the number for which calls will be redirected. The special symbol ? may be used
as a wildcard to represent any digit.
<redirect> Defines the placeholder used in the two-target routing entry and the number to which
calls to <x> will be redirected.
<sin> The service indicator variable sin restricts 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)
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 in-
dicators.
<time> Optional. For type 2 redirect entries, a timer (in seconds) can be defined after the service
indicator entry.
NOTE: In the entry is to apply for all service indicators, the value 00 must be defined for
<sin>.
CHAPT E R 5
57
Example: 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
BRI controller 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 BRI 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 ports Subscriber line in the pabx.cfg:
Example: 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]
5 . 3 . 2 VO I P P R O F I L E S
This section includes all of the most important parameters for communication with the VoIP peer.
MapAll00=40DF:00
Redirect340DF:=A
MapAllA=9
BUSY[<cause>] 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 BRI 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>]
CHAPT E R 5
58
Basic Parameters
Table 5.26 route.cfg: VoIP Basic Parameters
VoIP Basic Parameters
[Voip=<name>]
Name of the routing profile. The name must begin with a letter and should be short and meaningful.
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 peers IP address or name. Default is 0 (if it is not set, the parameter VoipIpMask should be set to
0x00000000).
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 profiles signaling protocol for outgoing VoIP calls. In the case of incoming calls, autorecog-
nition ensures that each call from the peer is accepted, regardless of the protocol:
0=H.323 (default), 1=SIP udp, 2=SIP tcp.
CHAPT E R 5
59
VoipCompression=<list>
The compression to be used, in order of preference. At least one matching codec with the peer must be de-
fined.
Voice:
g729, g729a, g729b, g729ab
These codecs have a bit rate of 8 kbit/s (compression ratio 1:8). A stands for Annex A and B for
Annex B.
g72616, g72624, g72632
These ADPCM codecs have various bit rates: g72616 = 16kBit/s (compression ratio 1:4), g72624
= 24kBit/s and g72632 = 32kBit/s (compression ratio 1:2).
NOTE: G726 32kBit/s can also be signaled as G.721 by using the entry g721.
g728
The Codec has a bit rate of 16kBit/s (compression ratio 1:4).
g711a, g711u
These PCM codecs have a bit rate of 64kBit/s. No voice compression occurs. a stands for a-law
and u for -law.
g723, g723L
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.
NOTE: This has no influence on the compression ratio of incoming RTP packets. Both sides must be able to
receive both ratios.
gsm
GSM-FR (full rate) has a bit rate of 13 kbit/s.
The following codecs are also possible: g721 (SIP only)
Fax: t38
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.
Data: trp
Transparent or clear mode (RFC 4040). Transparent relay of 64 kbit/s data streams.
gnx64
ccd
Clear-channel signaling (as per RFC3108)
Define a special profile for data call origination or destination numbers. Bear in mind that echo cancelation
in this VoIP profile might be switched off (VoipECE=no).
Table 5.26 route.cfg: VoIP Basic Parameters (continued)
CHAPT E R 5
60
Please refer to Chapter 8 for information on other possible entries.
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.
NOTE: For versions 13.0c or lower, we recommend that you also set the parameter
VoipDelayDisc to Yes to improve the ASR.
VoipSilenceSuppression=<mode>
Yes (default) activates silence suppression, CNG (comfort noise generation) and VAD (voice activity detec-
tion). No deactivates silence suppression.
NOTE: In SIP signaling, silence suppression is negotiated as per RFC3555.
VoipTxM=<num> 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 peers frame size will be used if it is smaller than the one defined. If you enter fix, the con-
figured factor will always be used.
Table 5.26 route.cfg: VoIP Basic Parameters (continued)
CHAPT E R 5
61
Management Parameters
5 . 3 . 3 G A T E K E E P E R P R O F I L E S
Gatekeeper profiles are used to connect the VoIPBOX BRI 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 gatekeep-
Table 5.27 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 the codec and the frame size used. . The IMSI
appears after the IP addresses if the keyword IMSI is defined in the pabx.cfg.
Example of a CDR entry:
21.08.07-11:01:42,21.08.07-11: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
CHAPT E R 5
62
ers. These gatekeeper profiles are then assigned to the VoIP profiles:
Table 5.28 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 BRIs defined prefix(es). Use a space to separate entries.
RasId=<name>
The alias used for gatekeeper registration.
GkId=<name>
The gatekeepers alias.
GkPwd=<name>
Password to log onto the gatekeeper. If you do not use authentication, leave this entry blank.
GkAdd=<ip addr>
The gatekeepers 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).
CHAPT E R 5
63
5 . 3 . 4 R E G I S T R A R P R O F I L E S
Registrar profiles are used to register the VoIPBOX BRI with a SIP registrar. It is possible to configure different reg-
istrars for different destinations and to define backup registrars. These registrar profiles are then assigned to the
VoIP profiles:
Table 5.29 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 registers request header. Bear in mind that the DNS service must be
active if you enter the host name.
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.
RegContact=<name or ip addr>
Used in the Contact: field.
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 TELES.VoIPBOX sends an empty UDP packet to the registrars
IP address. The packet is essentially an alive packet to avoid possible firewall problems.
CHAPT E R 5
64
5 . 3 . 5 R A D I U S P R O F I L E S
Radius profiles are used to connect the VoIPBOX BRI 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 5.30 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 servers 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.
CHAPT E R 5
65
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 en-
tered, the attribute will not be set (default).
Table 5.30 route.cfg: Radius Parameters (continued)
Radius Parameters
CHAPT E R 6
66
6 ROUT I NG EXAMPL ES
The following examples describe possible implementation scenarios for H.323, SIP and connection to a Radius serv-
er.
H.323
VoIPBOX BRI in an H.323 network (Chapter 6.2 )
Backbone router using a backup gatekeeper (Chapter 6.5 )
Backbone router with direct endpoint signaling (Chapter 6.6 )
SIP
VoIPBOX BRI as a second-generation LCR and registration with a SIP carrier (Chapter 6.1 )
Work@home scenario with signaling through a SIP proxy (Chapter 6.3 )
Authentication and accounting on a Radius server (Chapter 6.8 )
VoIP backup and automatic reactivation (Chapter 6.9 )
V O I P B O X B R I A S A S E C O N D - G E N E R A T I O N L C R
CHAPT E R 6
67
6 . 1 VO I P B OX B R I A S A S E C O N D - G E N E R A T I O N L C R
In the following example of a PBX connection,
all international calls are terminated to VoIP
(40). The VoIP carrier profile DF and the SIP
protocol are used. Block dialing is used, and
the last digit waits three seconds. National
calls are routed through the carrier with the
prefix 01078. All other calls are sent to the
PSTN unchanged. All calls from the PSTN or
from a VoIP carrier are sent directly to the NT
controller, to which the PBX is attached.
For the VoIP profile DF, the system uses the
registrar reg and registers with
myself.home.com, username user and
password pwd. SIP UDP is used for signaling.
A maximum of 8 media channels with the G.729 codec can be used. The peers IP address is 192.168.0.10.
Bear in mind that emergency calls must be routed to the PSTN.
[system]
DTMFWaitDial=3
MapAll00=|40DF:00<<24
MapAll0=9010780
MapOut?=9?
Restrict9=pl
Restrict40=pl
MapAllpl=10
[Voip=DF]
VoipDirection=IO
VoipPeerAddress=domain.com
VoipIpMask=0x00000000
VoipSignalling=1
VoipCompression=g729 g711a t38
VoipSilenceSuppression=Yes
VoipProxy=192.168.0.150
VoipOwnAddress=user@domain.com
VoipUser=user
VoipPwd=pwd
VoipMaxChan=8
VoipTxM=2
VoipRegistrar=reg
[Registrar=reg]
RegId=domain.com
RegOwnId=user.domain.com
RegUser=user
RegPwd=pwd
RegProxy=192.168.0.150
Ethernet
IP
Network
2 x BRI
2 x BRI
PSTN
i i
V O I P B O X B R I I N A N H . 3 2 3 N E T WO R K
CHAPT E R 6
68
6 . 2 VO I P B OX B R I I N A N H . 3 2 3 N E T WO R K
In the following example all voice calls from
the BRI NT lines (10) are routed through VoIP
(40) to the VoIP carrier with the profile name
DF. All calls from VoIP (40) are routed to the
BRI NT controller (10).
H.323 is used as the signaling protocol and a
gatekeeper is used in the VoIP network. Be-
cause the gatekeeper assigns and authorizes
the peer, only one VoIP profile is necessary.
Since the peers may use various compression
algorithms, you can define several if you so
choose.
The codec with the highest priority is G.729. If
the peer does not support it, G.72632, G.711a, G.711u and are also possible. Silence suppression is active.
The gatekeepers IP address is 192.168.0.10. This gatekeeper profile can handle up to 8 simultaneous VoIP calls.
The VoIPBOX BRIs alias is VoIPBOX01. The prefix is 0049. The gatekeepers alias is GK1 and no password is
used:
[System]
;To BRI
Restrict40=tobri
MapAlltobri=10
;To VoIP
MapAll?=40DF:?
[Voip=DF]
VoipDirection=IO
VoipPeerAddress=0.0.0.0
VoipSignalling=0
VoipCompression=g729 g72632 g711a g711u t38
VoipMaxChan=8
VoipTxM=4
VoipGk=GK1
[Gatekeeper=GK1]
RasPort=1719
OwnRasPort=1719
RasId=VoIPBOX01
RasPrefix=0049
GkId=GK
GkAdd=192.168.0.10
GkPwd=
GkTtl=300
GkMaxChan=8
IP
Network
4 x BRI
WO R K @H O ME S C E N A R I O WI T H S I G N A L I N G T H R O U G H A S I P P R O X Y
CHAPT E R 6
69
6 . 3 WO R K @H O ME S C E N A R I O WI T H S I G N A L I N G T H R O U G H A S I P P R O X Y
The following example of a route.cfg file the
company has two permanent employees work-
ing at home. The extension numbers 1111 and
2222 are assigned to these two users. All calls
with these destination numbers that come
from the PSTN, the connected SIP carrier pro-
file, and the attached ISDN PBX are routed di-
rectly with the two profiles User1 and User2 to
the employees. If these SIP phones are not reg-
istered, the calls are routed to the company's
operator. The symmetric RTP is also activated,
which avoids dead-air calls from remote users
that are behind a NAT firewall.
Example continued on next page:
Bear in mind that if names are used instead of IP addresses, the DNS service must be
activated.
[System]
;incoming traffic from PSTN and VoIP
Restrict9=pl
Restrict40=pl
;destination number routing for remote users
MapAll1111=40User1:1111
MapAll2222=40User2:2222
MapAllpl1111=40User1:1111
MapAllpl2222=40User2:2222
;redirect of calls in case the phones are not reach-
able
Redirect340User1:=red
Redirect340User2:=red
MapAllred1111=100
MapAllred2222=100
;all other calls from PSTN or VoIP send to ISDN PBX
unchanged
MapAllpl=10
; all calls from ISDN PBX to VoIP carrier except
remote users
DTMFWaitDial=5
MapAll0=|40DF:0<<24
MapAll1=|40DF:1<<24
MapAll2=|40DF:2<<24
MapAll3=|40DF:3<<24
MapAll4=|40DF:4<<24
MapAll5=|40DF:5<<24
MapAll6=|40DF:6<<24
MapAll7=|40DF:7<<24
MapAll8=|40DF:8<<24
MapAll9=|40DF:9<<24
MapAll*=|40DF:*<<24
MapAll#=|40DF:#<<24
Carrier
BRI
BRI
PSTN
BRI
SIP
IP
Network
i i
WO R K @H O ME S C E N A R I O WI T H S I G N A L I N G T H R O U G H A S I P P R O X Y
CHAPT E R 6
70
;VoIP profile for remote user
[Voip:User1]
VoipDirection=IO
VoipOwnUser=1111
VoipOwnPwd=pwd
VoipAuth=www
VoipExpires=600
VoipSignalling=1
VoipMaxChan=2
VoipTxM=2
VoipMediaWaitForConnect=Tone
VoipDtmfTransport=3
VoipRFC2833PayloadType=101
;SBC feature to avoid one way voice for peer sys-
tems behind NAT:
VoipAutoRtpAddr=Yes
VoipT303=5
[Voip:User2]
VoipDirection=IO
VoipOwnUser=2222
VoipOwnPwd=pwd
VoipAuth=www
VoipExpires=600
VoipSignalling=1
VoipMaxChan=2
VoipTxM=2
VoipDtmfTransport=3
VoipAutoRtpAddr=Yes
VoipT303=5
;VoIP profile to connect with the SIP network:
[Voip=DF]
VoipDirection=IO
VoipPeerAddress=sip-carrier.com
VoipIpMask=0xffffffff
VoipUser=user
VoipPwd=pwd
VoipSignalling=1
VoipMaxChan=8
VoipTxM=2
VoipDtmfTransport=3
VoipRegistrar=Reg
[Registrar=Reg]
RegId=sip-carrier.com
RegUser=user
RegPwd=pwd
RegExpires=3600
I S D N D I A L - U P F O R T E R MI N A T I N G V O I P C A L L S
CHAPT E R 6
71
6 . 4 I S D N D I A L - U P F O R TE R MI N A T I N G VO I P C A L L S
In the following example of the ip.cfg, the
VoIPBOX BRIs IP address is 192.168.1.2. No
default gateway is configured. The standard
route is assigned to the ISDN PPP interface.
When the packets to be routed (firewall config-
uration) set up this connection using dial-on-
demand, the ISDN dial-up Internet connection
with the number 12345 (Dad=) is set up to
terminate VoIP calls. the username is user
and the password is pwd.
The firewall settings allow only SIP UDP signal-
ing packets and RTP/RTCP packets for ports
29000-29015 in both directions. This can be
used in locations without broadband Internet
connection and generally have several simultaneous voice calls. Only one ISDN B-channel connection to the Inter-
net is set up, but up to six simultaneous voice calls can be transmitted (depending on the codec and options used).
If no voice call takes place over the dial-up connection for 20 seconds, the connection is torn down:
[System]
[emac0]
IpAddress=192.168.1.2/24
[xppp0]
Dad=12345
User=user
Pwd=pwd
Route=0.0.0.0
AuthProto=chap
IdleTO=20
MTU=1500
Rfc1662=0
[firewall]
#localnetwork
fw=pass out quick on emac0 from any to any
fw=pass in quick on emac0 from any to any
#loopback
#outgoing traffic
fw=pass out quick on xppp0 proto udp from any to any port eq 5060 keep state keep frags
...
#incoming traffic
fw=pass in quick on xppp0 proto udp from any to any port eq 5060 keep state keep frags
...
# other will be blocked
fw=block in log quick on xppp0 all
fw=block out log quick on xppp0 all
3 x BRI
1 x BRI
6 Simultaneous
VoIP Calls
IP
Network
PSTN
B A C K B O N E R O U T E R U S I N G A B A C K U P G A T E K E E P E R
CHAPT E R 6
72
6 . 5 B A C K B O N E R O U T E R U S I N G A B A C K U P G A T E K E E P E R
the BRI PBX line (10) are routed through VoIP
BRI NT controller (10).
A backup gatekeeper is used in addition to the
gatekeeper. Definition of more than one gate-
keeper occurs in individual gatekeeper profiles
(GK1 and GK2).
Because the various gatekeepers assign and
authorize the peer, only one VoIP profile is nec-
essary. When a gatekeeper ends registration or
does not respond, the next gatekeeper on the
list is automatically used. Compression G.729 and T.38 (fax) are used. Silence suppression is active.
The gatekeepers IP addresses are 192.168.0.10 and 192.168.0.12. These gatekeeper profiles can handle up to 8
simultaneous VoIP calls. The VoIPBOX BRIs alias is VoIPBOX01. The prefix is 0049. The gatekeepers aliases are
GK1 and GK2. No password is used.
The parameter VoipUseIpStack must be set in the VoIP profile.
IP
Network
Ethernet
4 x BRI
i i
B A C K B O N E R O U T E R U S I N G A B A C K U P G A T E K E E P E R
CHAPT E R 6
73
[System]
Restrict40=tobri
MapAlltobri=10
MapAll?=40DF:?
[Voip=DF]
VoipDirection=IO
VoipSignalling=0
VoipCompression=g729 t38
VoipMaxChan=8
VoipTxM=4
VoipGk=GK1 GK2
[Gatekeeper=GK1]
RasPort=1719
OwnRasPort=1719
RasId=VoIPBOX01
RasPrefix=0049
GkId=GK
GkAdd=192.168.0.10
GkPwd=
GkTtl=300
GkMaxChan=8
[Gatekeeper=GK2]
RasPort=1719
OwnRasPort=1719
RasId=VoIPBOX01
RasPrefix=0049
GkId=backupGK
GkAdd=192.168.0.12
GkPwd=
GkTtl=300
GkMaxChan=8
B A C K B O N E R O U T E R WI T H D I R E C T E N D P O I N T S I G N A L I N G ( H . 3 2 3 )
CHAPT E R 6
74
6 . 6 B A C K B O N E R O U T E R WI T H D I R E C T E N D P O I N T S I G N A L I N G ( H . 3 2 3 )
the VoIP line (40) are routed to the BRI NT con-
troller (10). All calls beginning with 0 coming
from the PBX are sent to the first VoIP peer and
all calls beginning with 1 are sent to the sec-
ond VoIP peer.
The first VoIP peers IP address is 172.16.0.30
(VoIP profile iG1). H.323 signaling is used.
Only compression G.729 and T.38 (fax) are
used. Silence suppression is active. A maxi-
mum of 4 VoIP connections can be set up using
this profile.
The second VoIP peers IP address is
172.16.0.40 (VoIP profile iG2). H.323 signaling is used. Only compression G.711a is used. A maximum of 4 VoIP
connections can be set up using this profile. You can use the IP address in the CDRs to differentiate calls from in-
dividual peers.
[System]
;To BRI
Restrict40=tobri
MapAlltobri=10
Restrict10=tovoip
MapAlltovoip0=40iG1:0
MapAlltovoip1=40iG1:1
[Voip=iG1]
VoipDirection=IO
VoipSignalling=0
VoipMaxChan=4
VoipTxM=4
VoipIpLogging=yes
[Voip=iG2]
VoipDirection=IO
VoipSignalling=0
VoipCompression=g711a
VoipSilenceSuppression=No
VoipMaxChan=4
VoipTxM=4
VoipIpLogging=yes
8 Channels
IP
Network
4 x BRI
4 Channels
4 Channels
I N T R A S T A R
CHAPT E R 6
75
6 . 7 I N T R A S TA R
In the following example of one of the two IntraSTAR capable devices route.cfg, a one-second interruption in
RTP/RTCP transmission from the VoIP peer is considered to be a disruption in the IP connection and results in fall-
back to ISDN. Another quality criterion is packet loss, whereby a fractionlost ratio of 10% in five seconds also re-
sults in fallback to ISDN. Bear in mind that silence suppresion must be deactivated. The IntraSTAR call resulting
from the fallback to ISDN is sent using the BTX service, and the ISDN controller is labled with 9:
[System]
;---------------
DTMFWaitDial=3
;IntraSTAR
MapAllIS=*0500*9
;Areacode 030 (Berlin, Germany)
MapOut110=9110
MapOut112=9112
MapOut0=|40DF:0<<25
MapOut1=|40DF:0301<<25
MapOut2=|40DF:0302<<25
MapOut3=|40DF:0303<<25
MapOut4=|40DF:0304<<25
MapOut5=|40DF:0305<<25
MapOut6=|40DF:0306<<25
MapOut7=|40DF:0307<<25
MapOut8=|40DF:0308<<25
MapOut9=|40DF:0309<<25
Redirect340DF:=pl
MapAllpl=9
MapIn0=100
MapIn1=101
MapIn2=102
MapIn3=103
MapIn4=104
MapIn5=105
MapIn6=106
MapIn7=107
MapIn8=108
MapIn9=109
[Voip:DF]
VoipDirection=IO
VoipPeerAddress=company_sub.de
VoipSilenceSuppression=No
VoipSignalling=1
VoipMaxChan=8
VoipTxM=2
VoipT303=3
VoipIntrastar=Yes
VoipBrokenDetectionTimeout=1000
VoipQualityCheck=FractionLost 5 10 10
B A C K B O N E R O U T E R A N D A U T H E N T I C A T I O N A N D A C C O U N T I N G WI T H A R A D I U S S E R V E R
CHAPT E R 6
76
6 . 8 B A C K B O N E R O U T E R A N D A U T H E N T I C A T I O N A N D A C C O U N T I N G WI T H
A R A D I U S S E R V E R
the BRI PBX line (10) are routed through VoIP
BRI NT controllers (10).
In the following example the Radius server rad
is used for authentication and accounting and
is implemented for the VoIP profile DF.The
username is user, the password is pwd and
the secret is secret. The system registers on
the Radius server
(radiusserver.domain.com) with the
host name myself.domain.com. H.323 is
used for signaling, with the voice codec G.729.
The peers IP address is 192.168.0.10. The same Radius server rad is used for accounting.
Bear in mind that if names are used instead of IP addresses, the DNS service must be activated.
[System]
;BRI
Restrict40=tobri
MapAlltobri=10
;To VoIP
MapAll?=40DF:?
[Voip=DF]
VoipDirection=IO
VoipSignalling=0
VoipMaxChan=8
VoipTxM=4
VoipRadiusAuthenticate=rad
VoipRadiusAccounting=rad
[Radius=rad]
Host=radiusserver.domain.com
User=user
Password=pwd
Secret=secret
OwnId=myself.domain.com
ServiceType=1
RequestTimeout=5
IP
Network
Ethernet
4 x BRI
V O I P B A C K U P A N D A U T O MA T I C R E A C T I V A T I O N
CHAPT E R 6
77
6 . 9 VO I P B A C K U P A N D A U T O MA T I C R E A C T I V A T I O N
The following example describes an automatic
VoIP peer change when ASR2 values result in
a connection that no longer corresponds with
the quality standards. Traffic with an ASR2 val-
ue of over 30% for the last 30 calls is sent to
IP address 172.16.0.80. When the ASR2 falls
below 30%, profile iG2 is used. After one
hour has passed, the connection quality at the
original peer is automatically tested. If the con-
nection corresponds with the quality stan-
dards, this peer is reactivated. Both profiles
use H.323 signaling. The voice codec is G.729
and faxes are transmitted with T.38. The frame
size is 40ms.
[Voip=iG1]
VoipDirection=Out
VoipSignalling=0
VoipMaxChan=8
VoipTxM=4
VoipQualityCheck=ASR2 30 30 3600
VoipOverflow=iG2
[Voip=iG2]
VoipDirection=Out
VoipSignalling=0
VoipMaxChan=8
VoipTxM=4
VoIP
Reactivation
Poor
Quality
IP
Network
VoIP
Backup
C O N F I G U R A T I O N E R R O R S
CHAPT E R 7
78
7 SYST EM MAI NT ENANCE AND SOF T WARE
UPDAT E
7 . 1 C O N F I G U R A T I O N E R R O R S
When typographical errors are made in the configuration files, an entry appears in the protocol.log when the
configuration is activated. This entry includes the line number and its contents.
7 . 2 S T A T U S A N D E R R O R ME S S A GE S
The protocol.log file assigned as the file for logging the protocol in the configuration file
(ActionLog=file) contains information on all activities within the system. In the example below, you can see
that all activities are recorded beginning with the date and time. If functions were activated by key combinations
from terminal devices you can identify these along with the service ID.
16.05.06-11:51:31,[990]Start STATUS - TELES.VoIPBOX V11.7a (007f)
16.05.06-12:10:57,[01A]ERR: Layer1
16.05.06-12:10:58,[000]ERR: OK
16.05.06-12:10:58,[010]ERR: OK
16.05.06-12:12:06,Remote Control from IP 192.168.1.2
16.05.06-12:12:06,Remote Control: OK
16.05.06-12:12:16,Activate Configuration System
16.05.06-12:16:26,Remote Control Terminated
16.05.06-14:00:00,Activate Configuration Night2
16.05.06-14:00:00,Time Switch Operation
16.05.06-18:00:00,Activate Configuration Night3
16.05.06-18:00:00,Time Switch Operation
Table 7.31 Event Log Messages
Message NMS Definition
Status Program
[990] Start STATUS X TELES system software and status program have been started.
System Start
[999] System-Boot X System restarted by timer.
[999] Remote Control:
Reboot
System restarted by remote administration command.
Configuration Changes
Activate configura-
tion <num> OK
Configuration <num> successfully loaded. Initiator displayed in
next line.
Activate configura-
tion <num> failed
[<err>]
Configuration <num> could not be loaded.
S T A T U S A N D E R R O R ME S S A G E S
CHAPT E R 7
79
Remote Control: Date
& Time changed
Date and/or time were changed via remote administration.
Time Switch Operation The configuration change was made by the timer.
Remote Administration
Remote Control from
<peer>, <Remote-
Code>, <service>, 0
Remote administration access from number or IP address.
Remote Control: OK Successful remote administration access.
[993]Remote Control:
wrong password
X Remote administration access was denied because of a wrong pass-
word.
[994]Remote Control:
wrong number
X Remote administration access was denied because the call originat-
ed from an unauthorized number (RemoteOrigination).
Remote Control
Terminated <start
time>,<end time>,
<num>, <RemoteCode>,
<service>, 0
Remote administration session from <num> ended. Session length
is indicated by start time and end time.
Errors Reported by the Status Program
[<port><i>] ERR:
Problem at Port <num>
X A Layer 1 or Layer 2 error occurred on <num>.
<i> indicates error type:
A Layer 1 error
; Layer 2 error
0 Layer 1&2 operational.
4 RSSI (for mobile only)
Should the error persist, a differentiation is possible through 'status
of the ports'.
If this message appears, status inquiry connections via remote ad-
ministration are accepted and NMS downloads the
protocol.log file.
NOTE: If the RSSI falls below the value configured in the
pabx.cfg, the port will shut down automatically.
Attention: No Call-
back-Call <num> Ar-
rived
Callback with DTMF: the Callback Provider <num> did not call back
within approx. 20 sec.
Direct Line Access with DTMF: the call was accepted but disconnect-
ed again within x sec. (as defined by MapCallBack-
WaitDisc).
Table 7.31 Event Log Messages (continued)
CHAPT E R 7
80
The following status and error messages appear in the protocol.log file when ALARM appears in the VoIP
ports subscriber line:
Write error Access to the disk drive on which the data is to be stored was not
possible because it is set for read-only, full or because of faulty
hardware or software.
[995] Msg-Memory >
75%
X This message appears when message memory is over 75% full.
If this message appears, status inquiry connections via remote ad-
ministration are accepted and NMS downloads the
protocol.log file.
Table 7.32 Protocol Log Status and Error Messages
Message Definition
System Configuration (a)
config: <num> duplicate
profile
Specified line in pabx.cfg or route.cfg contains duplicate
profile.
config: <num> invalid Specified line in pabx.cfg or route.cfg is invalid.
config: evaluation errcode
<num>
Internal error.
Port-Specific Entries
[<port>]Unblock Port The <port> has been unblocked. This can occur via remote access
for all controller types or automatically via vGATE for mobile chan-
nels.
[<port>]Block Port The <port> has been blocked. This can occur via remote access for
all controller types or automatically via vGATE for mobile channels.
[<port>]Restart Port The <port> has been blocked. This can occur via remote access for
all controller types or automatically via vGATE for mobile channels.
Ethernet Interface
[99d]ERR: emac<num><state> The Ethernet controllers status is checked every minute and any
change in status is noted.
<num> Number of the EMAC interface (0 or 1).
<state> up Ethernet link is active
down Ethernet link is inactive
Table 7.31 Event Log Messages (continued)
CHAPT E R 7
81
!resolve ip-address ARP request for specified IP address failed.
pingcheck failed Ping to configured server failed for configured amount of time; host
might reboot this port.
Voice Packetizer Task (b)
[<port>]ERR: OK, <count>
devices
The number (<count>) of DSPs were loaded during startup with-
out errors. The first VoIP controller appears in [<port>].
[<port>]ERR: init failed A DSP could not be loaded. This DSP or the first VoIP controller is
defined in [<port>].
VP: <channel> <msg> Voice-packetizer chips report fatal error on specified channel, with
specified message.
VoIP (c)
GK <name> URC Successful UnRegister from specified gatekeeper.
GK <name> GRJ <num> GatekeeperRequest was rejected
GK <name> RCF Successful RegistrationRequest (RegistrationConfirm).
GK <name> RRJ <num> RegistrationRequest was rejected.
GK <name> ARJ <dad> <num> AdmissionRequest was rejected.
GK <name> !ACF dad AdmissionRequest was not answered.
GK <name> !GCF GatekeeperRequest was not answered.
no profile for ipaddress Incoming VoIP call from specified IP address was rejected due to no
matching VoIP profile.
registrar <name>: registra-
tion done
Successful registration at SIP registrar.
registrar <name>: wrong
auth-type <num>
Registrar does not perform MD5 for authentication.
registrar <name>: gives no
nonce
Nonce missing in response from registrar (possible error in registrar
configuration).
registrar <name>: registra-
tion forbidden
Registration with specified registrar is not allowed.
registrar <name> not an-
swering
Specified registrar does not respond.
voipconn oad->dad broken Voice codec chips report broken RTP connection.
Table 7.32 Protocol Log Status and Error Messages (continued)
Message Definition
CHAPT E R 7
82
voip FdInitAll failed
<cause>
Internal failure.
voip ISDNListen failed Internal failure.
voipIpSocketInit failed Internal failure.
!DNS-lookup <hostname> DNS lookup for specified host name failed (DNS not activated? Miss-
ing or invalid DNS server?).
message from <ip addr> not
decodable
H323, ASN1 packet cannot be decoded.
vGATE
[99]ERR: SimUnit !connect An outgoing connection to the vGATE Sim Unit could not be estab-
lished.
[99]ERR: ControlUnit <ip
addr> !connect
An outgoing connection to the vGATE Control Unit could not be es-
tablished.
Number Portability
[99i]ERR: np !connect Connection to the iMNP could not be established.
[99i]ERR: np connect <ip ad-
dr>
Connection to the iMNP reestablished.
System Kernel (e)
task <name> suspended specified task was suspended due to internal error; host might re-
boot this port.
Mail (f)
cdr !connect <ip addr> sending CDR: TCP connect to specified IP address failed.
mail !connect <ip addr> sending e-mail: TCP connect to specified IP address failed.
Radius (g)
!DNS-lookup <hostname> DNS lookup for specified host name failed (DNS not activated? Miss-
ing or invalid DNS server?).
timeout auth <ip addr> Authentication request to specified Radius server failed due to tim-
eout.
timeout acnt <ip addr> Accounting request to specified Radius server failed due to timeout.
!rsp-auth <ip addr> Response authenticator from specified Radius server was invalid
(wrong secret/password?).
!auth <ip addr> <num> Authentication denied by specified Radius server.
Message Definition
CHAPT E R 7
83
Configuration Errors in the ip.cfg
Error in ip.cfg line <line>: section [<section_name>] unknown
Error in ip.cfg line <line>: parameter "<parameter_name>" in
[<section_name>] unknown
Error in ip.cfg line <line>: parameter "<parameter_name>" does not belong
to any Section
There is an error in the NAT Configuration
The NAT was not loaded, please check the Configuration for mistakes
There is an error in the DHCPD Configuration
The DHCP SERVER was not loaded, please check the Configuration for mistakes
There is an error in the ALTQD Configuration
The ALTQD SERVER was not loaded, please check the Configuration for mistakes
There is an error in the FIREWALL Configuration
The FIREWALL was not loaded, please check the Configuration for mistakes
Error in <dsl_interface> Connection failed. Please, connect a cable in the
<ethernet> port
Error in <dsl_interface>: Connection Failed. Please, revise your Username/
Password configuration
Error in <dsl_interface>: Connection Failed. Please, revise the DSL Modem
Message Definition
S O F T WA R E U P D A T E
CHAPT E R 7
84
7 . 3 S O F T WA R E U P D A T E
You may find that you would like to implement features that are only possible with a more recent software version.
To update the software on your system, follow these instructions.
Check the software version running on your system to make sure the one you want to install is newer. The basic
software consists of the following files:
start
netbsdz
netbsdfs.gz
vbox.tz1
Make sure there is enough available memory for the new version. We recommend that you delete unnecessary log
files and back-ups. Do NOT delete or rename existing software files before updating.
Make sure no traffic is running on the system while updating the system. Do not turn
the system off during the update.
These files form a unit and belong to the same software version. To avoid compati-
bility conflicts, check with TELES service before you update the software.
Upload the new files ONLY via GATE Manager. Do not use any other process (e.g. FTP)
to update the software files. This can lead to irreversible damage to the operating
system.
If an error message appears during the update process, no NOT restart or turn off the
system! Make a note of the error message and the update steps that have been taken
and contact TELES service.
! !
i i
! !
i i
S O F T WA R E U P D A T E
CHAPT E R 7
85
Once the files have been completely transferred, check the file size and reboot the system. As soon as you can reach
the system via GATE Manager again, check the version number of the running software.An update of the following
optional function modules (see Chapter 13 ) occurs in the same way. Make sure the file extension has the same
running number as that of the file on the system:
HTTP User Interface:
httpd.tz2
httpd.izg
iPBX:
ipbx.tz2
ipbx.izg
DNS forwarder:
dnsmasg.tz2
SNMP agent:
snmpd.tz0
IP update:
ipupdate.tz2
The only exception is that you must shut down the modules that have *.izg files before updating. To shut down
these modules, change the name of or delete the corresponding *.tz* file and restart the system.
Following transfer of the *.izg file, you must rename the *.tz.* file again and restart the system.
T R A C E
CHAPT E R 7
86
7 . 4 TR A C E
During operation, the trace readouts of the VoIPBOX BRI can be saved in a file or transmitted with remote main-
tenance directly. The trace options must be turned on in the GATE Manager (offline or online trace) or via FTP raw
commands (see Chapter 4.11.3 ). Trace results presented here are for BRI and VoIP interfaces, and for the fol-
lowing services in various levels:
Figure 7.13 GATE Manager: Online Trace Activation Window
VoIPBOX BRIes offer two different types of trace:
Online - trace information is immediately displayed in the GATE Managers trace window.
Offline - trace information is written to a file on the VoIPBOX BRI.
Table 7.33 Trace Options
Option Definition
Mail Output for all SMTP packets.
NumberPortability Output of all packets for communication with the iMNP.
vGATE Output of all packets for communication with the vGATE.
VoiceCodecs Output of RTCP information described under VP module.
PPP Output of PPP connection information.
DTMF Output for DTMF tone recognition.
Remote Output for GATE Manager and NMS communication.
T R A C E
CHAPT E R 7
87
VoIPBOX BRI systems create trace files when the TraceLog=file entry is present in the pabx.cfg. Traces
can be activated via remote administration (GATE Manager or FTP).
Trace Output Format
The following entries appear at the beginning and end of each trace:
DD.MM.YY-hh:mm:ss.ss, Start
DD.MM.YY-hh:mm:ss.ss, End
DD = day
hh = hour
MM = month
mm = minute
YY = year
ss.ss = hundredths of seconds
Traces appear in the following format:
[<hh:mm:ss>] <module>[<port>]: <trace>
<module>
s = send for PRI/BRI ports
r = receive for PRI/BRI ports
x = send to VoIP destinations
y = receive from VoIP destinations
i = information messages and internal trace outputs between VoIP and the other interfaces (ISDN)
a = VoIP controllers RTCP output
m = mail output
g = remote output
<port>
port number (controller number in the pabx.cfg) or 255 if a service is used
<trace>
output in the defined syntax for the module
7 . 4 . 1 I S D N TR A C E O U T P U T
Trace output for DSS1 and SS7 is in hexadecimal notation. You can use the external tool TraceView.exe to
translate offline trace output. You will find the tool in the Software folder on the enclosed CD. The
GATE Managers trace window can also display translated online traces.
Please bear in mind that the volume of trace readouts can grow quite large, so that
faulty transmission of the trace data may result with remote maintenance. A trace at
full capacity can cause the system to crash.
i i
T R A C E
CHAPT E R 7
88
Example: The following example shows an untranslated DSS1 trace:
7 . 4 . 2 VO I P TR A C E O U T P U T
As described above in Chapter 7.4 , there are four modules for VoIP traces. The groups x (send), y (receive) and
i (information and internal output) appear when a Layer2 or Layer3 offline or online trace is started. Group a
(RTCP output) only appears when the module Voice Codecs is active.
Particularly in the case of VoIP connections (protocols H.323 and SIP), the trace output is quite extensive and ab-
breviations make it difficult to keep track of the results. The following list contains a description of H.323 output.
Output for the signaling protocol SIP is transmitted in ASCII and translated for better legibility. Since they are dis-
played unabridged, no description is necessary. Information and internal output traces correspond with the H.323
output and are described in the following tables. For ENUM, please refer to Chapter 7.4.2.6 .
In general, the following rules apply for this trace output:
The information is thoroughly analyzed where it is received (all rcv messages).
17.05.06-09:54:40,Start 11.7a (L3)
[09:55:14.58] r[00]: 00 01 02 02 08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 6c 02 81 31 70 06 81 31 32 33
34 35 7d 02 91 81
[09:55:14.58] s[00]: 02 01 02 04 08 02 80 02 0d 18 03 a9 83 81
[09:55:14.58] s[01]: 00 01 a8 9a 08 02 00 46 05 04 03 80 90 a3 18 03 a1 83 89 6c 02 81 31 70 06 81 31 32 33
34 35 7d 02 91 81
[09:55:14.58] r[01]: 02 01 9a aa 08 02 80 46 0d 18 03 a9 83 89
[09:55:14.86] r[01]: 02 01 9c aa 08 02 80 46 01
[09:55:14.86] s[00]: 02 01 04 04 08 02 80 02 01
[09:55:16.73] r[01]: 02 01 9e aa 08 02 80 46 07 29 05 05 07 01 09 33 4c 07 01 81 31 32 33 34 35
[09:55:16.73] s[01]: 00 01 aa a0 08 02 00 46 0f
[09:55:16.73] s[00]: 02 01 06 04 08 02 80 02 07 29 05 05 07 01 09 32 4c 07 01 81 31 32 33 34 35
[09:55:16.73] r[00]: 00 01 04 08 08 02 00 02 0f
[09:55:44.30] r[00]: 00 01 06 08 08 02 00 02 45 08 02 80 90
[09:55:44.35] s[01]: 00 01 ac a0 08 02 00 46 45 08 02 80 90
[09:55:46.71] r[01]: 02 01 a0 ae 08 02 80 46 4d
[09:55:46.71] s[01]: 00 01 ae a2 08 02 00 46 5a
[09:55:46.71] s[00]: 02 01 08 08 08 02 80 02 4d
[09:55:46.71] r[00]: 00 01 08 0a 08 02 00 02 5a
17.05.06-09:51:33,End
Table 7.34 H.323 Output
Packet Description
h225 H.225-protocol messages.
h245 H.245-protocol messages.
pstn Messages of the internal protocol interface that provides the interface to the other inter-
faces PRI, BRI and GSM.
rcv Coming from the IP network or the internal protocol interface; appears with <dir> in
the trace lines.
snd Sending to the IP network or the internal protocol interface; appears with <dir> in the
trace lines.
T R A C E
CHAPT E R 7
89
7 . 4 . 2 . 1 I N T E R F A C E I P N E T WO R K
Establish H.323 Session
Usually there is trace output that displays a new H.323 session. The direction is crucial (whether the call is going
into or coming out of the IP network).
H.225 Signaling Output
The following trace results are for a call coming from the IP network. rcv will appear at <dir> and signifies the
direction:
h225connect to <ip address> cr <cr> s <si>
h225accept from <ip address> s <si>
Table 7.35 H.323 Session
Trace Output Description
connect to Outgoing VoIP call
accept from Incoming VoIP call
<ip address> Peer's IP address
cr <cr> Call reference (corresponds with the internal protocol interface's PSTN call
reference)
s <si> Session ID
h225<dir> tpkt msg 0x<mt> h225cr <cr> addr <ip address>
Table 7.36 H.225 Signaling
<mt> The ETS message type in hexadecimal; can consist of values listed in Table
7.37.
<hcr> H.225 call reference in hexadecimal (does not have to be unique when calls
come from multiple peers).
<ip address> The peer's IP address.
T R A C E
CHAPT E R 7
90
The following lines show the packet contents in detail:
Table 7.37 ETS Message Types
Hex Value Message Type
1 Alerting
2 Call Proceeding
3 Progress
5 Setup
7 Connect
D Setup Acknowledge
5A Release Complete
62 Facility
6E Notify
7B Information
7D Status
h225 decode rc 0, q931 msg 0x<mt> = 0, len <length>
h225<type> <mt> voipcfg addr <ip address> rc 0 compr <codec>
h225<type> <mt> h225cr <hcr> FS:<bool> (<codec>,<ip address>,<port>) TUNN:<bool>
H245:<bool>(<ip address>,<port>)
h225<type> <mt> h225cr <hcr> cr <cr>
Table 7.38 Incoming VoIP Calls
<mt> Message type in hexadecimal as per ETS standard (see Table 7.37) or written
out as a name.
len <length> Packet length in bytes.
h225<type> H.225 rcv or send; received or sent from the IP network.
addr <ip address> Peer's IP address.
compr <codec> Peer's compression list (see Table 7.39).
FS<bool> FastStart offered in the signaling packet or not.
T R A C E
CHAPT E R 7
91
(<codec>, Lists codecs offered (seeTable 7.61).
<ip address>, Peer's IP address for RTP data.
<port>) Peer's port for RTP Data.
Tunn<bool> Shows whether or not tunneling is offered as a signaling variant.
H245<bool> Shows an extra H.245 session.
(ip address, Peer's IP address.
port) Peer's port.
h225cr <hcr> H.225 message's call reference (does not have to be unique when calls
come from multiple VoIP peers).
cr <cr> Internal call reference (always unique for the call).
ALT:<ip ad-
dress>:<port>,<DAD>
Optional alternative values for IP address port or a new destination number
for a facility message with the cause call forwarded.
Table 7.39 Compression Codecs Used
Synonym Codec
A G.711Alaw64k
B G.711Ulaw64k
C G.7231
D G.728
E G.729
F gsmFullRate
G T.38fax
O G.729A
P G.72616
Q G.72624
R G.72632
S G.729B
Table 7.38 Incoming VoIP Calls (continued)
T R A C E
CHAPT E R 7
92
When the call is sent in the direction of the IP network, the trace will include only the most important information:
Or:
T G.729AB
U G.729E
V G.723L
W Transparent
X G.721
Y iLBC20
Z iLBC30
h225<type> <mt1> dad <num> cr <cr>
Table 7.40 Calls to the IP Network 1
<mt> Message type written out; if a decimal number appears here, it will be translated as per
Table 7.37.
<num> Called party number.
<cr> Call reference.
h225<type> callproc typ <mt> cr <cr>
Table 7.41 Calls to the IP Network 2
<mt> The ETS message type in hexadecimal.
Table 7.39 Compression Codecs Used (continued)
Synonym Codec
T R A C E
CHAPT E R 7
93
7 . 4 . 2 . 2 R T P / R T C P O U T P U T
The RTP/RTCP output displays whether the signaling information corresponds with the contents of the compression
chips. The output occurs when a media channel is set up or torn down:

VP Module
rtp start cr <cr> ch <ch> li <li> ri <ri> st <st> fx <fx> cp <comp> txm <factor>
Table 7.42 RTP/RTCP Output
<ch> The internal media channel used.
<li> 1 appears when the local RTP address (and port) has been defined.
<ri> 1 appears when the remote RTP address (and port) have been established.
<st> 0 appears if the channel's voice packetizer has not yet been started. 1 appears if the
voice packetizer can receive, but not send. 2 appears when the voice packetizer can
receive and send.
<fx> 1 appears when T.38 (fax) is used, otherwise 0.
<comp> The codec used, as per Table 7.39.
<factor> Multiplication factor for default frame size (20ms, 30 ms for G.723).
rtp stop cr <cr>1 ch <ch>
Table 7.43 RTP Stop Message
T R A C E
CHAPT E R 7
94
This module's output shows the controller packets for the voice connections. That means that the RTCP packets
and relevant information also appear.
The following results occur for a new RTP connection:

The following output shows the channels state in the compression chip during a startup or change of codec:
The following output shows whether the compression chip starts sending and receiving packets:
Sent and received bytes appear with the following output results:
a[<controller>]: <VoIPcodecChipType> start(val) ch=<ch> local=<port> remote=<ip address:port> agg=<bool>
Table 7.44 RTP/RTCP Output (VP Module)
<controller> Running number for the VoIP controller.
<VoIPcodecChipType> Stands for the type designation for the compression chips used (e.g. Ac49x).
<val> Shows which connection is set up.
<port> RTP port.
<ip address> Peer's IP address in hexadecimal.
agg=<bool> 1 means an RTP-multiplex connection is used (default 0).
a[<controller>]: <VoIPcodecChipType>OpenChannelConfiguration ch=<ch> rc=0
a[<controller>]: <VoIPcodecChipType>T38ChannelConfiguration ch=<ch> rc=0
a[<controller>]: <VoIPcodecChipType>ActivateRegularRtpChannelConfiguration ch=<ch> rc=0
a[<controller>]: <VoIPcodecChipType> ch <ch> establish
a[<controller>]: <VoIPcodecChipType> ch <ch>: in <byte> out <byte>
Table 7.45 RTP Packet Statistics
<byte> The call's received or sent bytes.
T R A C E
CHAPT E R 7
95
The following output shows the jitter buffer status:
a[<controller>]: <VoIPcodecChipType> ch <ch> rtcp<dir> <num> ji <ji> rt <rt> fl <fl> in <byte> out <byte>
Table 7.46 RTCP Packet Statistics
rtcp<dir> R sender report (received) is more interesting, since it comes from the peer. T sender re-
port (transmitted).
<num> 0 ReceiverReport packet
1 SenderReport packet
2 Packet requested by the driver
<ji> Delay jitter [msec].
<rt> Round-trip local<->remote, round-trip delay [msec].
<fl> Fraction lost: Fraction of packets lost [8lsb].
<cl> Cumulative lost: number of lost packets [24lsb].
a[<controller>]: <VoIPcodecChipType> ch <ch> jitter buffer n1 n2 n3n4 n5 n6 n7 n8
Table 7.47 Jitter Buffer Status
n1 SteadyStateDelay in milliseconds
n2 NumberOfVoiceUnderrun
n3 NumberOfVoiceOverrun
n4 NumberOfVoiceDecoderBfi (bfi = bad frame interpolation)
n5 NumberOfVoicePacketsDropped
n6 NumberOfVoiceNetPacketsLost
n7 NumberOfIbsOverrun (ibs = in band signaling)
T R A C E
CHAPT E R 7
96
An RTP connection has ended when the following trace output appears:
The following output results when the codec changes for a fax connection:
n8 NumberOfCasOverrun
a[<controller>]: <VoIPcodecChipType> stop ch=<ch>
Table 7.48 RTP Stop Message (VP Module)
a[<controller>]: ac49x ch <ch> fax/data n1 n2 n3
Table 7.49 Codec Change for Fax
n1 Fax bypass flag:
0 Voice, data bypass or fax relay
1 Fax bypass
n2 Signal detected on decoder output (see Table 7.50)
n3 Signal detected on encoder input (see Table 7.50)
Table 7.50 faxordatasignalevent
Value Definition Description
0 SILENCE_OR_UNKNOWN Undefined (unknown signal or silence)
1 FAX_CNG CNG-FAX (calling fax tone, 1100 Hz)
Table 7.47 Jitter Buffer Status (continued)
T R A C E
CHAPT E R 7
97
Fax relay is activated for the corresponding channel:
The following output shows various values for fax transmission (see Table 7.51 for a description of the values):
2 ANS_TONE_2100_FAX_CED_OR_
MODEM
FAX-CED or modem-ANS (answer tone,
2100 Hz)
3 ANS_TONE_WITH_REVERSALS ANS (answer tone with reversals)
4 ANS_TONE_AM ANSam (AM answer tone)
5 ANS_TONE_AM_REVERSALS ANSam (AM answer tone with reversals)
6 FAX_V21_PREAMBLE_FLAGS FAX-V.21 preamble flags
7 FAX_V8_JM_V34 FAX-V.8 JM (fax call function, V.34 fax)
8 VXX_V8_JM_VXX_DATA V.XX-V.8 JM (data call function, V-series
modem)
9 V32_AA V.32 AA (calling modem tone, 1800 Hz)
10 V22_USB1 V.22 USB1 (V.22(bis) unscrambled binary
ones)
11 V8_BIS_INITIATING_DUAL_TONE V.8bis initiating dual tone (1375 Hz and
2002 Hz)
12 V8_BIS_RESPONDING_DUAL_TONE V.8bis responding dual tone (1529 Hz and
2225 Hz)
13 VXX_DATA_SESSION V.XX data session
14 V21_CHANNEL_2 V.21 channel 2 (mark tone, 1650 Hz)
15 V23_FORWARD_CHANNEL V.23 forward channel (mark tone, 1300 Hz)
16 V21_CHANNEL_1=18 V.21 channel 1 (mark tone, 980 Hz)
17 BELL_103_ANSWER_TONE Bell 103 answer tone, 2225 Hz
18 TTY TTY
19 FAX_DCN FAX-DCN (G.3 fax disconnect signal)
a[<controller>]: Ac49xActivateFaxRelayCommand(1) ch <ch> rc <cr>
a[<controller>]: ac49x ch <ch> faxrelay: n1 n2 n3 n4 n5 n6 n7 n8 n9 n10 n11 n12 n13 n14
Table 7.50 faxordatasignalevent (continued)
Value Definition Description
T R A C E
CHAPT E R 7
98
Table 7.51 Fax Status
Value Description
n1 UnableToRecoverFlag (0 no, 1 yes)
n2 IllegalHdlcFrameDetectedFlag (...)
n3 FaxExitWithNoMcfFrameFlag
n4 HostTransmitOverRunFlag
n5 HostTransmitUnderRunFlag
n6 InternalErrorFlag
n7 ReceivedBadCommandFlag
n8 TimeOutErrorFlag
n9 TxRxFlag (0 receive, 1 transmit)
n10 T30State
0 FAX_RELAY_T30_STATE__INITIALIZATION
1 FAX_RELAY_T30_STATE__CNG
2 FAX_RELAY_T30_STATE__CED
3 FAX_RELAY_T30_STATE__V21
4 FAX_RELAY_T30_STATE__NSF
5 FAX_RELAY_T30_STATE__NSC
6 FAX_RELAY_T30_STATE__CSI
7 FAX_RELAY_T30_STATE__CIG
8 FAX_RELAY_T30_STATE__DIS
9 FAX_RELAY_T30_STATE__DTC
10 FAX_RELAY_T30_STATE__NSS
11 FAX_RELAY_T30_STATE__TSI
12 FAX_RELAY_T30_STATE__DCS
13 FAX_RELAY_T30_STATE__CTC
14 FAX_RELAY_T30_STATE__CRP
15 FAX_RELAY_T30_STATE__DCN
16 FAX_RELAY_T30_STATE__PRE_MESSAGE_RESPONSE
17 FAX_RELAY_T30_STATE__POST_MESSAGE_RESPONSE
18 FAX_RELAY_T30_STATE__POST_MESSAGE_COMMAND
19 FAX_RELAY_T30_STATE__VXX
20 FAX_RELAY_T30_STATE__TCF
21 FAX_RELAY_T30_STATE__IMAGE
T R A C E
CHAPT E R 7
99
The following output appears when the compression chip recognizes DTMF tones:
n11 NumberOfTransferredPages
n12 BadInputPacketId
n13 BadInputPacketTotalSize
n14 FaxBitRate
1 FAX_BIT_RATE__300_BPS
a[<controller]: ac49x ch <ch> ibs <dtmf> <dir> <mode> <lev> <dur>
Table 7.52 DTMF Tone Recognition
<ch> Media channel
<dtmf> Recognized DTMF tone in the stream or as per RFC2833
<dir> Direction
0 Coming from BRI/analog
1 Coming from VoIP
<mode> 0 Tone has ended
1 Tone has been recognized
<lev> Signal level in -dBm
<dur> Tone duration
Table 7.51 Fax Status (continued)
Value Description
T R A C E
CHAPT E R 7
100
7 . 4 . 2 . 3 I N T E R N A L P R O T O C O L I N T E R F A C E ( T O I S D N, P OT S, MO B I L E )
These trace outputs always begin with the keyword pstn, followed by the direction and the message type. The
message is then either concluded or other information follows:
Output also appears when a call comes from the internal protocol interface and is assigned to a VoIP profile. The
characters appear in front of the colon in the routing entry:
Assignment of media channel used for the internal interface and the ISDN call reference for the VoIP call's appears
as follows:
pstn<type> <mt1> dad <num> oad <num> cr <cr> s <si> ch <chan> isdncr<icr>
Table 7.53 Internal Protocol Interface
<type> Direction from (rcv) or to (snd) the internal protocol interface.
<mt1> Message type written out; if a decimal number appears, it will be translated as per Table
7.37.
<num> DAD<num> = called party number, OAD<num> = calling party number.
<si> Session ID.
<chan> Media channel used.
<icr> Call reference for the internal protocol interface (DSS1).
pstnrcv get_voipcfg <voip profile>
Table 7.54 Received from PSTN 1
<voip profile> Defines the VoIP profile to be used.
pstnrcv bchanind cr <cr> ch <chan> isdncr <icr>
T R A C E
CHAPT E R 7
101
7 . 4 . 2 . 4 H . 2 4 5 ME S S A GE S
The following trace output is possible:
Following this trace output, either a detailed description of the message and its corresponding message type, in-
cluding negotiating information, or trace output elements that are explained later appear. The most important mes-
sage types that contain further information elements are as follows:
Table 7.55 Received from PSTN 2
<chan> Media channel used for the internal protocol interface (DSS1).
<icr> Call reference for the internal protocol interface (DSS1).
h245<dir>(<tt>) cr <cr>
Table 7.56 H.245 Messages
<dir> The message's direction; rcv (incoming from the peer) or snd (sent message).
<tt> H.245 transport type.
<cr> Internal call reference.
... TerminalCapabilitySet peer=<comp> cfg=<comp>
... TerminalCapabilitySet <comp>
Table 7.57 Codec Used
<comp> List of compression codecs offered (see Table 7.39), the list of the peer's codecs appears
behind peer, and cfg shows which codecs are defined in the VoIP profile
T R A C E
CHAPT E R 7
102
The trace output is as follows when the message type is not translated or is ignored:
... OpenLogicalChannel cn=<cn> cpr=<comp> sessid=<sid> ctrl=<ip address>:<rtcp port>
... OpenLogicalChannelAck cn=<cn> sessid=<sid> media=<ip address>:<rtp port>
Table 7.58 Logical Channel Parameters
<cn> H.245 channel number per H.225 connection.
<sid> Session ID.
<comp> Codec used (see Table 7.39).
<ip address> Protocol peer IP address.
<rtcp port> Port used for the protocol RTCP.
<rtp port> Port used for the protocol RTP.
h245<dir>(<tt>) cr <cr> unknown msg <hmt> <hmi>
Table 7.59 H.245 Parameters
hmt The H.245 message type (multimedia system control message type), (Table 7.60).
hmi The H.245 message ID (see Table 7.61, Table 7.62, Table 7.63, Table 7.64).
Table 7.60 Multimedia System Control Message Types
ID Message
0 (Table 7.61) Request
1 (Table 7.62) Response
2 (Table 7.63) Command
T R A C E
CHAPT E R 7
103
Depending on the system control message type, one of the following message IDs appear:
3 (Table 7.64) Indication
Table 7.61 Message IDs for Request Message
ID Message
0 NonStandard
1 MasterSlaveDetermination
2 TerminalCapabilitySet
3 OpenLogicalChannel
4 CloseLogicalChannel
5 RequestChannelClose
6 MultiplexEntrySend
7 RequestMultiplexEntry
8 RequestMode
9 RoundTripDelayRequest
10 MaintenanceLoopRequest
11 CommunicationModeRequest
12 ConferenceRequest
13 MultilinkRequest
14 LogicalChannelRateRequest
Table 7.62 Message IDs for Response Message
ID Message
0 NonStandard
1 MasterSlaveDeterminationAck
2 MasterSlaveDeterminationReject
Table 7.60 Multimedia System Control Message Types (continued)
ID Message
T R A C E
CHAPT E R 7
104

3 TerminalCapabilitySetAck
4 TerminalCapabilitySetReject
5 OpenLogicalChannelAck
6 OpenLogicalChannelReject
7 CloseLogicalChannelAck
8 RequestChannelCloseAck
9 RequestChannelCloseReject
10 MultiplexEntrySendAck
11 MultiplexEntrySendReject
12 RequestMultiplexEntryAck
13 RequestMultiplexEntryReject
14 RequestModeAck
15 RequestModeReject
16 RoundTripDelayResponse
17 MaintenanceLoopAck
18 MaintenanceLoopReject
19 CommunicationModeResponse
20 ConferenceResponse
21 MultilinkResponse
22 LogicalChannelRateAcknowledge
23 LogicalChannelRateReject
Table 7.63 Message IDs for Command Message
ID Message
0 NonStandard
1 MaintenanceLoopOffCommand
Table 7.62 Message IDs for Response Message (continued)
ID Message
T R A C E
CHAPT E R 7
105
2 SendTerminalCapabilitySet
3 EncryptionCommand
4 FlowControlCommand
5 EndSessionCommand
6 MiscellaneousCommand
7 CommunicationModeCommand
8 ConferenceCommand
9 h223MultiplexReconfiguration
10 NewATMVCCommand
11 MobileMultilinkReconfigurationCommand
Table 7.64 Message IDs For Indication Message
ID Message
0 NonStandard
1 FunctionNotUnderstood
2 MasterSlaveDeterminationRelease
3 TerminalCapabilitySetRelease
4 OpenLogicalChannelConfirm
5 RequestChannelCloseRelease
6 MultiplexEntrySendRelease
7 RequestMultiplexEntryRelease
8 RequestModeRelease
9 MiscellaneousIndication
10 JitterIndication
11 h223SkewIndication
12 NewATMVCIndication
Table 7.63 Message IDs for Command Message (continued)
ID Message
T R A C E
CHAPT E R 7
106
7 . 4 . 2 . 5 R A S ( R E G I S T R A T I O N , A D MI S S I O N , S T A T U S )
As a general rule, the most important terminal and gatekeeper messages appear written out with the gatekeeper's
IP address (<ip addr>):

13 UserInput
14 h2250MaximumSkewIndication
15 McLocationIndication
16 ConferenceIndication
17 VendorIdentification
18 FunctionNotSupported
19 MultilinkIndication
20 LogicalChannelRateRelease
21 FlowControlIndication
22 MobileMultilinkReconfigurationIndication
H225 GatekeeperRequest to <ip addr> (s 131)
H225 GatekeeperConfirm <ip addr>
H225 GatekeeperReject <ip addr> reason <reason>
Table 7.65 RAS
<reason> Gatekeeper reject reason, see Table 7.69.
H225 GkRegistration to <ip addr>
H225 RegistrationConfirm <ip addr>
H225 RegistrationReject <ip addr> reason <reason>
Table 7.64 Message IDs For Indication Message (continued)
ID Message
T R A C E
CHAPT E R 7
107
All other messages appear as follows:
Table 7.66 Gatekeeper 1
<reason> Registration reject reason, see Table 7.70.
H225 GkResourcesAvailableIndicate to <ip addr> (<act chan> <max chan>)
H225 ResourcesAvailableConfirm <ip addr>
H225 GkAdmission cr <cr> to <ip addr>
H225 AdmissionConfirm <ip addr> cr <cr>
H225 AdmissionReject <ip addr> reason <reason>
<reason> Admission reject reason, see Table 7.71.
H225 GkDisengage cr <cr> to <ip addr>
H225 DisengageConfirm <ip addr>
H225 UnregistrationRequest <ip addr>
H225 GkUnregistrationConf to <ip addr>
H225 unknown msg from Gk <ip addr>: <code>
T R A C E
CHAPT E R 7
108
<code> Unknown gatekeeper message, see Table 7.72.
Table 7.69 Gatekeeper Reject Reason
ID Reject Reason
0 resourceUnavailable
1 terminalExcluded
2 invalidRevision
3 undefinedReason
4 securityDenial
5 genericDataReason
6 neededFeatureNotSupported
Table 7.70 Registration Reject Reason
ID Reject Reason
0 DiscoveryRequired
1 InvalidRevision
2 InvalidCallSignalAddress
3 InvalidRASAddress
4 DuplicateAlias
5 InvalidTerminalType
6 UndefinedReason
7 TransportNotSupported
8 TransportQOSNotSupported
T R A C E
CHAPT E R 7
109
9 ResourceUnavailable
10 InvalidAlias
11 SecurityDenial
12 RullRegistrationRequired
13 AdditiveRegistrationNotSupported
14 InvalidTerminalAliases
15 GenericDataReason
16 NeededFeatureNotSupported
Table 7.71 Admission Reject Reason
ID Reject Reason
0 CalledPartyNotRegistered
1 InvalidPermission
2 RequestDenied
3 UndefinedReason
4 CallerNotRegistered
5 RouteCallToGatekeeper
6 InvalidEndpointIdentifier
7 ResourceUnavailable
8 SecurityDenial
9 QosControlNotSupported
10 IncompleteAddress
11 AliasesInconsistent
12 RouteCallToSCN
13 ExceedsCallCapacity
14 CollectDestination
Table 7.70 Registration Reject Reason (continued)
ID Reject Reason
T R A C E
CHAPT E R 7
110
15 CollectPIN
16 GenericDataReason
17 NeededFeatureNotSupported
Table 7.72 Unknown Gatekeeper Messages
ID Message
0 GatekeeperRequest
1 GatekeeperConfirm
2 GatekeeperReject
3 RegistrationRequest
4 RegistrationConfirm
5 RegistrationReject
6 UnregistrationRequest
7 UnregistrationConfirm
8 UnregistrationReject
9 AdmissionRequest
10 AdmissionConfirm
11 AdmissionReject
12 BandwidthRequest
13 BandwidthConfirm
14 BandwidthReject
15 DisengageRequest
16 DisengageConfirm
17 DisengageReject
18 LocationRequest
19 LocationConfirm
Table 7.71 Admission Reject Reason (continued)
ID Reject Reason
T R A C E
CHAPT E R 7
111
7 . 4 . 2 . 6 E N U M O U T P U T
This output is assigned to group i and occurs with Layer2 and Layer3 traces:
20 LocationReject
21 InfoRequest
22 InfoRequestResponse
23 NonStandardMessage
24 UnknownMessageResponse
25 RequestInProgress
26 ResourcesAvailableIndicate
27 ResourcesAvailableConfirm
28 InfoRequestAck
29 InfoRequestNak
30 ServiceControlIndication
31 ServiceControlResponse
i[<controller>]: enum_query cr <CR> ch <CH>: <num> -> <length> <<answer pattern>>
Table 7.73 ENUM Output
<ch> Media channel.
<num> Phone number converted into ENUM domain format.
<length> Length of the answer field in the DNS response in bytes. 0 appears if the number was
not found.
<answer pat-
tern>
Displays the DNS response. 0 appears if the number was not found.
Table 7.72 Unknown Gatekeeper Messages (continued)
ID Message
T R A C E
CHAPT E R 7
112
7 . 4 . 2 . 7 E X A MP L E S
The following examples are offline traces. You can generate them using the GATE Manager or FTP commands. The
filename is trace.log. The following cases appear in the examples:
Incoming H323 Call with FastStart (Chapter )
Outgoing H323 Call with FastStart (Chapter )
Fax Call (Chapter )
T R A C E
CHAPT E R 7
113
Incoming H323 Call with FastStart
[15:04:09.12] i[04]: h225accept from 172.16.0.100 s 4
[15:04:09.15] y[04]: h225rcv tpkt msg 5 h225cr 8006 addr 172.16.0.100 pt 0
[15:04:09.16] y[04]: h225 decode rc 0, q931 msg 5 (0), len 361
[15:04:09.16] y[04]: h225rcv setup voipcfg addr 172.16.0.100 rc 0 <DF> compr EABG
[15:04:09.16] y[04]: h225rcv faststart <A4B4E4G0>
[15:04:09.16] y[04]: h225rcv setup oad 01 00 <1111> <> dad 01 <321> rad <> bc 038090a3 0101
[15:04:09.16] y[04]: h225rcv setup h225cr 8006 FS:1(E,172.16.0.100,29000) TUNN:1 H245:0(0,0)
[15:04:09.16] y[04]: h225rcv setup h225cr 8006 cr 5
[15:04:09.16] i[04]: pstnsnd setup dad 1 oad 1111 cr 5 s 4
[15:04:09.16] s[02]: 02 ff 03 08 01 02 05 04 03 80 90 a3 18 01 89 6c 06 01 81 31 31 31 31 70 04 81 33 32
31 7d 02 91 81
[15:04:09.16] i[04]: pstnrcv connresp cr 5 acc 5 ch 1
[15:04:09.16] x[04]: h225snd callproc typ d cr 5 pri 0
[15:04:09.50] r[02]: 00 81 20 1a 08 01 82 01 18 01 89
[15:04:09.50] s[02]: 00 81 01 22
[15:04:09.50] i[04]: pstnrcv alert cr 5 cls ff
[15:04:09.50] i[04]: rtp start cr 5 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 2
[15:04:09.50] x[04]: h225snd callproc typ 1 cr 5 pri 8
[15:04:09.52] a[04]: ac49x start(201) ch=0 local=29000 remote=ac100064:29000 agg=0
[15:04:09.52] a[04]: Ac49xOpenChannelConfiguration ch=0 rc=0
[15:04:09.52] a[04]: Ac49xT38ChannelConfiguration ch=0 rc=0
[15:04:09.52] a[04]: Ac49xActivateRegularRtpChannelConfiguration ch=0 rc=0
[15:04:09.63] a[04]: ac49x ch 0 rtcpR 0 ji -1 rt -1 fl 65535 in 0 out -1
[15:04:09.63] a[04]: ac49x ch 0 establish
[15:04:09.98] a[04]: ac49x ch 0 jitter buffer 75 0 0 0 1 0 0 0
[15:04:11.79] r[02]: 00 81 22 1a 08 01 82 07 4c 03 00 80 31
[15:04:11.79] s[02]: 02 81 1a 24 08 01 02 0f
[15:04:11.79] i[04]: pstnrcv connresp cr 5 acc 10 ch 255
[15:04:11.79] x[04]: h225snd callproc typ 7 cr 5 pri 0
[15:04:11.89] r[02]: 02 81 01 1c
[15:04:12.49] a[04]: ac49x ch 0 rtcpT 1 ji 201 rt 0 fl 0 in 290 out 394
[15:04:12.49] a[04]: ac49x ch 0: in 1552 out 1646
[15:04:16.23] a[04]: ac49x ch 0 rtcpR 1 ji 196 rt 84 fl 0 in 3236 out 3236
[15:04:17.98] r[02]: 00 81 24 1c 08 01 82 45 08 02 80 90
[15:04:17.98] s[02]: 00 81 01 26
[15:04:17.98] i[04]: pstnrcv terminate connection (3201) cr 5 cau 90 err 0 state 16 ch 1 rsid 1
[15:04:17.98] i[04]: rtp stop cr 5 ch 1
[15:04:17.98] x[04]: h225snd relack cr 5 cau 0x90
[15:04:17.98] i[04]: h225connection s 4 close
[15:04:17.98] i[04]: CloseSysFd 4 (st 22)
[15:04:18.03] s[02]: 02 81 1c 26 08 01 02 4d
[15:04:18.03] a[04]: ac49x ch 0: in 20486 out 21288
[15:04:18.03] a[04]: ac49x stop ch=0
[15:04:18.24] r[02]: 02 81 01 1e
[15:04:18.28] r[02]: 00 81 26 1e 08 01 82 5a
T R A C E
CHAPT E R 7
114
Outgoing H323 Call with FastStart
[15:25:13.61] r[02]: 00 81 2a 1e 08 01 48 05 04 03 80 90 a3 18 01 83 6c 05 00 80 31 31 31 70 07 81 31 32
33 34 35 36 7d 02 91 81
[15:25:13.61] s[02]: 00 81 01 2c
[15:25:13.61] s[02]: 02 81 1e 2c 08 01 c8 0d 18 01 8a
[15:25:13.61] i[04]: pstnrcv setup dad DF:123456 oad 111 cc 0 id dd006
[15:25:13.61] i[04]: pstnrcv get_voipcfg <DF>
[15:25:13.61] i[04]: h225connect to 172.16.0.100 cr 6
[15:25:13.61] x[04]: h225snd setup dad 123456 cr 6
[15:25:13.69] r[02]: 02 81 01 20
[15:25:13.69] y[04]: h225rcv tpkt msg d h225cr 6 addr 172.16.0.100 pt 8018c000
[15:25:13.69] y[04]: h225 decode rc 0, q931 msg d (11), len 32
[15:25:13.69] y[04]: h225rcv msg d (11) h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)
[15:25:14.36] y[04]: h225rcv tpkt msg 1 h225cr 6 addr 172.16.0.100 pt 8018c000
[15:25:14.36] y[04]: h225rcv faststart <E4>
[15:25:14.36] y[04]: h225rcv alert h225cr 6 FS:1(E,172.16.0.100,29000) TUNN:1 H245:0(0,0)
[15:25:14.36] s[02]: 02 81 20 2c 08 01 c8 01 1e 02 82 88
[15:25:14.39] a[04]: ac49x start(201) ch=0 local=29000 remote=ac100064:29000 agg=0
[15:25:14.41] r[02]: 02 81 01 22
[15:25:15.59] y[04]: h225rcv tpkt msg 7 h225cr 6 addr 172.16.0.100 pt 8018c000
[15:25:15.59] y[04]: h225rcv connect h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)
[15:25:15.59] i[04]: pstnsnd connect cr 6
[15:25:15.59] s[02]: 02 81 22 2c 08 01 c8 07 29 05 06 03 18 0f 19
[15:25:15.65] r[02]: 02 81 01 24
[15:25:15.93] r[02]: 00 81 2c 24 08 01 48 0f
[15:25:15.93] s[02]: 00 81 01 2e
[15:25:16.98] a[04]: ac49x ch 0: in 8836 out 7874
[15:25:20.10] a[04]: ac49x ch 0: in 20084 out 18802
[15:25:24.71] r[02]: 00 81 2e 24 08 01 48 45 08 02 80 90
[15:25:24.71] s[02]: 00 81 01 30
[15:25:24.71] i[04]: rtp stop cr 6 ch 1
[15:25:24.71] i[04]: CloseSysFd 4 (st 22)
[15:25:24.71] s[02]: 02 81 24 30 08 01 c8 4d
[15:25:24.79] a[04]: ac49x ch 0: in 37858 out 34096
[15:25:24.79] a[04]: ac49x stop ch=0
[15:25:24.92] r[02]: 02 81 01 26
[15:25:24.92] r[02]: 00 81 30 26 08 01 48 5a
T R A C E
CHAPT E R 7
115
Fax Call
[16:00:33.87] r[02]: 00 81 54 2c 08 01 01 05 04 03 80 90 a3 18 01 83 7d 02 91 81
[16:00:33.87] s[02]: 02 81 2c 56 08 01 81 0d 18 01 89 1e 02 82 88
[16:00:36.99] r[02]: 00 81 56 2e 08 01 01 7b 70 02 81 31
[16:00:37.17] r[02]: 00 81 58 2e 08 01 01 7b 70 02 81 32
[16:00:37.33] r[02]: 00 81 5a 2e 08 01 01 7b 70 02 81 33
[16:00:37.54] r[02]: 00 81 5c 2e 08 01 01 7b 70 02 81 34
[16:00:40.46] s[02]: 02 81 2e 5e 08 01 81 02 1e 02 82 88
[16:00:40.46] i[04]: pstnrcv setup dad DF:1234 oad cc 0 id 11d007
[16:00:40.46] i[04]: pstnrcv get_voipcfg <DF>
[16:00:40.46] i[04]: h225connect to 172.20.0.100 cr 7
[16:00:40.46] x[04]: h225snd setup dad 1234 cr 7
[16:00:40.46] y[04]: h225rcv tpkt msg d h225cr 7 addr 172.20.0.100 pt 800e7000
[16:00:40.46] y[04]: h225 decode rc 0, q931 msg d (11), len 32
[16:00:40.46] y[04]: h225rcv msg d (11) h225cr 7 FS:0(-,0,0) TUNN:1 H245:0(0,0)
[16:00:40.54] a[04]: ac49x start(201) ch=0 local=29000 remote=0:0 agg=0
[16:00:40.69] y[04]: h225rcv tpkt msg 1 h225cr 7 addr 172.20.0.100 pt 800e7000
[16:00:40.69] y[04]: h225rcv faststart <E4>
[16:00:40.69] y[04]: h225rcv alert h225cr 7 FS:1(E,172.20.0.100,29000) TUNN:1 H245:0(0,0)
[16:00:40.69] s[02]: 02 81 30 5e 08 01 81 01 1e 02 82 88
[16:00:40.70] a[04]: ac49x start2 ch=0 remote=ac100064:29000 rc=0
[16:00:40.91] y[04]: h225rcv connect h225cr 7 FS:0(-,0,0) TUNN:1 H245:0(0,0)
[16:00:40.92] i[04]: pstnsnd connect cr 7
[16:00:40.92] s[02]: 02 81 32 5e 08 01 81 07 29 05 06 03 18 10 00
[16:00:41.95] a[04]: ac49x ch 0: in 940 out 7926
[16:00:43.15] a[04]: ac49x ch 0 fax/data 0 0 1
[16:00:43.15] a[04]: ac49x ch 0 fax/data 0 0 0
[16:00:43.30] a[04]: Ac49xActivateFaxRelayCommand(1) ch 0 rc 0
[16:00:43.30] a[04]: ac49x ch 0 fax detected(1)
[16:00:43.30] i[04]: vpinfo fax detected cr 7 ch 1
[16:00:43.30] i[04]: h245snd(1) cr 7 TerminalCapabilitySet <EG>
[16:00:43.30] y[04]: h225rcv facility h225cr 7 FS:0(-,0,0) TUNN:1 H245:0(0,0)
[16:00:43.30] i[04]: h245rcv(1) cr 7 TerminalCapabilitySetAck
[16:00:43.33] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 2 0 0 0 0
[16:00:43.50] i[04]: h245rcv(1) cr 7 TerminalCapabilitySet peer=<EG> cfg=<EG>
[16:00:43.50] i[04]: h245snd(1) cr 7 TerminalCapabilitySetAck
[16:00:43.50] i[04]: h245snd(1) cr 7 RequestModeT38
[16:00:43.68] i[04]: h245rcv(1) cr 7 RequestModeAck
[16:00:43.68] i[04]: h245snd(1) cr 7 CloseLogicalChannel cn=1
[16:00:43.68] i[04]: h245snd(1) cr 7 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.200:29001
[16:00:43.69] i[04]: h245rcv(1) cr 7 CloseLogicalChannel cn=1 (1)
[16:00:43.69] i[04]: h245snd(1) cr 7 CloseLogicalChannelAck cn=1
[16:00:43.72] i[04]: h245rcv(1) cr 7 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.100:29001
[16:00:43.72] i[04]: h245snd(1) cr 7 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.200:29000
T R A C E
CHAPT E R 7
116
7 . 4 . 3 R E MO T E O U T P U T
This trace option provides output for communication with the GATE Manager or NMS. To activate this option, ac-
tivate the section Remote in the GATE Manager. You can choose the depth of the trace output: Error is limited
to error messages; Debug provides information; Detail provides the entire packet.
Output is defined with a g, and the port number is 99.
The following output shows an established GATE Manager connection:
[16:00:43.72] i[04]: h245rcv(1) cr 7 CloseLogicalChannelAck cn=1
[16:00:43.72] i[04]: h245rcv(1) cr 7 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.100:29000
[16:00:43.72] i[04]: rtp start cr 7 ch 1 li 1 ri 1 st 3 fx 0 cp G txm 1
[16:00:43.72] i[04]: rtp start cr 7 ch 1 li 1 ri 1 st 3 fx 1 cp G txm 1
[16:00:43.79] a[04]: ac49x start2 ch=0 remote=ac100064:29000 rc=0
[16:00:43.79] a[04]: ac49x start fax ch=0 doing fax already
[16:00:46.70] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 3 0 0 0 0
[16:00:48.95] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 8 0 0 0 0
[16:00:49.60] a[04]: ac49x ch 0 fax/data 0 0 6
[16:00:49.60] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 3 0 0 0 0
[16:00:51.53] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 12 0 0 0 0
[16:00:51.65] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 20 0 0 0 4
[16:00:52.94] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 20 0 0 0 4
[16:00:54.25] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 3 0 0 0 0
[16:00:55.73] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 16 0 0 0 0
[16:00:56.44] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 21 0 0 0 4
...
[16:01:25.93] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 21 0 0 0 4
[16:01:27.13] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 3 0 0 0 0
[16:01:28.26] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 18 0 0 0 0
[16:01:29.05] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 3 0 0 0 0
[16:01:30.56] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 1 17 1 0 0 0
[16:01:31.62] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 3 1 0 0 0
[16:01:32.72] a[04]: ac49x ch 0 faxrelay 0 0 0 0 0 0 0 0 0 15 1 0 0 0
[16:01:33.13] r[02]: 00 81 5e 34 08 01 01 45 08 02 80 90
[16:01:33.13] i[04]: rtp stop cr 7 ch 1
[16:01:33.13] i[04]: CloseSysFd 4 (st 22)
[16:01:33.16] s[02]: 02 81 34 60 08 01 81 4d
[16:01:33.16] a[04]: ac49x ch 0: in 5714 out 99508
[16:01:33.16] a[04]: ac49x stop ch=0
[16:01:33.22] r[02]: 00 81 60 36 08 01 01 5a
g[99]:moip: accept rc=2 ipad=<ip address> port=<port>
Table 7.74 Remote Output
<ip address> Remote systems IP address with GATE Manager.
T R A C E
CHAPT E R 7
117
All other trace output appears in detail mode in ASCII and are also translated.
7 . 4 . 4 S MT P TR A C E O U T P U T
This trace option provides output for communication with the mail server that occurs when status information or
files are sent.
To activate this option, activate the section Mail in the GATE Manager. You can choose the depth of the trace
output: Error is limited to error messages; Debug provides information; Detail provides the entire packet.
Output is defined with a m, and the port number is 99.
Sending Files or Status Information
Global message output:
<port> Origination port for the GATE Manager connection.
g[99]:moip: <direction> <length>
Table 7.75 Remote Output
<direction> recv Packets received from the remote system
send Packets sent to the remote system
write Output for communication with the internal remote interface
read Output for communication from the internal remote interface
<length> Data length in bytes.
m[99]:mail: sendmail (<length>)
Table 7.74 Remote Output (continued)
T R A C E
CHAPT E R 7
118
Detailed message output:
Receiving E-Mail Messages and Sending Them as SMS or USSD
The following output displays communication of an incoming SMTP connection:
Table 7.76 SMTP Output: Sending Files or Status Info
m[99]:mail: sendmail: <Faccount> <ip address> <Taccount> <domain> <subject> <content>
Table 7.77 SMTP Output: Sending Files or Status Info
<Faccount> Senders e-mail account (cdr, alarm, file, etc.).
<ip address> SMTP servers IP address.
<Taccount> Recipients e-mail account.
<domain> Recipients domain.
<subject> Content of the subject field; serial number of the sender system.
<content> Content of the messages body.
m[99]:mail: accept: ipad=<ip address> port=<port>
Table 7.78 SMTP Output: Receiving E-Mail and Sending as SMS or USSD
<ip address> The SMTP peer systems IP address.
<port> The SMTP peer systems origination port.
T R A C E
CHAPT E R 7
119
The following output displays which packets are sent to the SMTP peer:
The following output displays which packets are received from the SMTP peer:
The following output shows that the SMTP connection is being closed:
The mail module now converts the e-mail message to the internal format and then sent as SMS or USSD. Bulk mail
(several recipient entries for the same e-mail) appear as individual messages:

m[99]:mail: mysend <<content>>
<content> Content of the transmitted packet.
m[99]:mail: recv (<length>)
m[99]:mail: terminate_session
m[99]:mail: newMail2Host r=<Taccount> f=<Faccount> s=<subject> d=<content>
<Faccount> One entry from the senders To field.
T R A C E
CHAPT E R 7
120
The following output appears when the message has been successfully sent:
This is converted in the confirmation message, with the subject sent. The output in the subsequent communica-
tion with the mail server are identical to those described above in Sending Files or Status Information.
The following output appears when errors occur during transmission of the SMS or USSD message:
Message transmission was faulty and will be repeated:
Retried message transmission was also faulty, and an e-mail will be generated:
The output in the subsequent communication with the mail server are identical to those described above in Send-
ing Files or Status Information.
Receiving SMS or USSD and Sending as E-Mail
The following output shows the internal format when an SMS or USSD message is sent to the mail module. This
output is generated when transmission of the SMS or USSD message was not possible:
All other trace output appears in detail mode in ASCII and are also translated. The output in the subsequent com-
munication with the mail server are identical to those described above in Sending Files or Status Information.
<Taccount> Content of the From field.
<subject> Content of the subject field; usually not used.
<content> Content of the messages body; is sent as SMS or USSD.
m[99]:mail: rcvmail <Faccount> -> <Taccount>, done
m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed, will retry (<num>)
Table 7.82 SMTP Output: Transmission Error
<num> Current number of retries.
m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed <num> times
m[99]:mail: DATA_IND (<length>)
Table 7.81 SMTP Output: Receiving E-Mail and Sending as SMS or USSD (continued)
T R A C E
CHAPT E R 7
121
7 . 4 . 5 N U MB E R P O R T A B I L I T Y TR A C E O U T P U T
This trace option provides output for the communication with the iMNP database. To activate this option, activate
the section Number Portability in the GATE Manager. Output is defined with an n, and the port number is 99.
The following output appears when the system sets up a TCP session with the iMNP is being set up:
The following output shows that the connection has been established:
The following output shows that the connection attempt failed:
The following output shows a keep alive packet from the iMNP to keep the TCP session open:
Response to a number portability request that results in the calls routing:
n[99]:np: connecting to <ip addr>
Table 7.83 Number Portability Output: Connection with iMNP
<ip address> The iMNP systems IP address.
n[99]:np: connect to <ip addr> ok
n[99]:np: connect to <ip addr> failed
n[99]:np: recv <>
n[99]:np: recv <N<num>>
Table 7.84 Number Portability Output: Response
<num> Ported or unported number provided by the database.
T R A C E
CHAPT E R 7
122
7 . 4 . 6 D T MF TO N E TR A C E O U T P U T
Output about the setup of connections with the DTMF module and DTMF tone recognition are debugged. The out-
put differentiates between the groups err and inf. Output is defined with a d, and the port number is that of
the virtual DTMF controller:
The following output shows incoming call setup to the DTMF module:
The following output shows transmitted signaling messages depending on the call state:
d[<ctrl>]: dtmf: msg <call state>, unknown id <id>, from 14
Table 7.85 DTMF Output: Incoming Call Setup
<ctrl> The virual controllers running number.
<call state> 3101 Incoming setup
3201 Disconnect request
<id> Call identification number.
d[<ctrl>]: dtmf <message type> <id> <call state> 0
Table 7.86 DTMF Output: Signaling Messages
<message type> Send_d_connectFor setup acknowledge and connect.
send_alert_indFor alert.
send_disconnectFor disconnect
<id> Call identification number.
<call state> 3110 Incoming setup
3102 Disconnect request
3804 Alert
3202 Disconnect confirmation
T R A C E
CHAPT E R 7
123
The following output shows that the media channel has been designated for DTMF tone recognition:
The following output shows the output for negotiated DTMF tones:
d[<ctrl>]: dtmf send_alloc <b_chan id_unset> <ctrl>/<b chan>
Table 7.87 DTMF Output: Media Channel Designation
<b chan> Internal media channel used.
<b_chan
id_unset>
Media channel identification (in unset state).
d[<ctrl>]: dtmf: msg <msg>, id <b_chan id>, from 1, id <id>/<b_chan id_unset>
Table 7.88 DTMF Output: Media Channel Designation
<msg> 502 Media channel confirmation
102 Connect confirmation
602 Media channel free confirmation
d[<ctrl>]: dtmf send_info_ind <id> <<dtmf tone>>
I N T R A S T A R
CHAPT E R 8
124
8 SI GNAL I NG AND ROUT I NG FEAT URES
8 . 1 I N T R A S TA R
This feature uses Intranet/Internet (packet-based networks) and the ISDN network (line-based network) to transmit
voice calls. It ensures uninterrupted voice transmission when voice quality over the Intranet/Internet becomes un-
supportable. How the voice data arrives at the peer is irrelevant.
Automatic fallback to ISDN occurs in the following situation:
During call setup (when the target number cannot be reached through the Intranet/Internet).
During the call (when the voice quality no longer corresponds with the customers requirements).
If the voice quality improves to the defined level during the call, transmission of the voice data will automatically
revert to the Intranet/Internet, and the IntraSTAR ISDN connection will be torn down.
Bear in mind that both devices that handle the connections via VoIP or ISDN must be IntraSTAR capable for this
feature to work.
To activate this feature, configure the following entries in the route.cfg:
MapAllIS=*<service type>*<port>
The keyword IS activates IntraSTAR routing.
The type of service appears first on the right side of the equal sign, followed by the ISDN port to which the
IntraSTAR setup will be sent. The following type of service values are possible:
0500 (BTX)
0700 (data)
The following parameters must be set in the corresponding VoIP profile:
VoipIntrastar=yes
VoipBrokenDetectionTimeout=<ms>
VoipQualityCheck=<type minsamples limit recovertime>
For an example of the IntraSTAR function, please see Chapter 6.7 .
8 . 2 D I G I T C O L L E C T I O N ( E N B L O C K / O V E R L A P R E C E I V I N G )
This function makes it possible to collect digits and transmit calls when a specific number of digits has been dialed.
The entire call number is required for the call to be set up with a mobile phone or the mobile gateway. Since most
numbers have a uniform number of digits, the mobile gateway can collect digits when calls enter the gateway in
overlap mode. Digit collection occurs through the following mapping command:
MapAll<direct>=|<num><<<digits>
The | (pipe) signifies that the following digits will be collected before they are transmitted, and <digits> is the total
number of the port digits and the digits of the called party number. This figure can range between 00 and 24 and
must be entered in double digits. The parameter DTMFWaitDial defines the number of seconds the system waits
between the individual digits (default 5). Please bear in mind that you can configure a maximum of 11 digits in the
first part of the command and 19 (including a special character, e.g. #) in the second. The call will be forwarded
as soon as the specified number of digits has been dialed or a time-out limit has been reached.
R E J E C T I N G D A T A C A L L S A N D S P E C I F I E D N U MB E R S
CHAPT E R 8
125
The following example shows a call with the prefix 01555. The | (pipe) signifies that the following digits will be
collected before they are transmitted. The 14 at the end is the sum of the port digits and the digits of the called
party number (e.g. |#20=3, 01555899666=11, 3+11=14).
8 . 3 R E J E C T I N G D A T A C A L L S A N D S P E C I F I E D N U MB E R S
This chapter describes the configuration options for exclusion of data calls, prefixes, or call numbers from the rout-
ing process.
8 . 3 . 1 B L A C K L I S T R O U T I N G
The system will reject all calls directly if the MapAll entry contains the keyword & followed by the two-digit cause
value (see ETS 300 102-1).
MapAll<direct>=&<cause>
Example: In the following example, all calls to the number 004915551234 and all service calls with the
prefix 0180 are rejected with a busy signal. All other calls are sent to the VoIP profile DF:
8 . 3 . 2 WH I T E L I S T R O U T I N G
The following entries enable exclusion of specific OADs or trunk groups:
Restrict<ns>=<pl>
MapAll<pl>=&<cause>
NS refers to the internal controller number and the calls origination address.
Example: In the following example, the numbers 12345 and 12346 connected to the PBX at port 10 can-
...
MapAll01555=|#2001555<<14
...
DTMFWaitDial=5
...
A maximum of 5000 MapAll entries per time zone can be defined. For more than 5000
entries, please use the Teles iMNP.
MapAll015551234=&91
MapAll004915551234=&91
MapAll0180=&91
MapAll0=40DF:0
...
MapAll9=40DF:9
A maximum of 1000 Restrict entries per time zone can be defined.
i i
i i
R E J E C T I N G D A T A C A L L S A N D S P E C I F I E D N U MB E R S
CHAPT E R 8
126
not make any international calls. All national calls are sent to the VoIP profile DF and all local
calls are sent to the PSTN:
8 . 3 . 3 R E J E C T I N G C A L L S WI T H I S D N B E A R E R C A P A B I L I T Y D A T A
ISDN data calls can be handled differently from voice calls depending on the configuration of the call types DATA
or VOICE. This setting is especially interesting for VoIP or GSM calls:
MapAll<direct>=&<cause> <mode>
Example: In the following example, all ISDN data calls are rejected with the cause value AA (switching
equipment congestion). All calls with the prefix 0170 are routed to the mobile trunk group 26211
and all other calls are routed through VoIP:
8 . 3 . 4 S P E C I F I C R O U T I N G O F D A T A C A L L S V I A VO I P
In the ISDN network, data calls have a special service type. When an ISDN PBX is connected to a VoIP network, it
must continue to work without any problems (e.g. PBX remote maintenance calls or ISDN terminal adapter). In the
case of VoIP, a specific RTP payload type is used: trp, ccd or gnx64.
Example: In the following example, two VoIP profiles are configured, so that all calls are routed, regardless
of whether they are data calls or voice over IP calls. The first one is for outgoing voice calls and
all calls from VoIP to ISDN. The second profile is exclusively for outgoing data calls, so that sig-
Restrict1012346=int
MapAllint00=&91
MapAllint0=40DF:0
MapAllint1=91
...
MapAllint9=90
Analog modem connections are not included in this configuration, as they generally
do not have a specified bearer capability.
MapAll0=&aa DATA
...
MapAll9=&aa DATA
...
MapAll0170=262110170
MapAll0=40DF:0
...
MapAll9=40DF:9
i i
C L I P A N D C L I R
CHAPT E R 8
127
naling consists solely of clear mode in SDP:
8 . 4 C L I P A N D C L I R
8 . 4 . 1 R O U T I N G C L I P A N D C L I R C A L L S
This function allows you to route calls with Calling Line Identification Presentation (CLIP) differently from calls with
Calling Line Identification Restriction (CLIR). For example, all CLIP calls can be rejected, so that only calls that do
not present the calling number or calls without a calling party number (e.g. analog) are transmitted through the
VoIPBOX BRI.
Use the following configuration to define the various routing methods:
InsertCLIR=On activates this mode. 01 is the service indicator for telephony (analog and ISDN) and is used to
differentiate these calls from remote administration calls. Restrict9=OK 01 means that all telephony calls
without a calling number are put through. Restrict|9=OK 01 means that all CLIR telephony calls are put
through. Restrict90=FAIL 01 means that all CLIP telephony calls are rejected with No Channel Available
as rejection cause when they are mapped to MapInFAIL=&aa.
8 . 4 . 2 S E T T I N G C L I R
Setting a hash (#) in front of a call number makes it possible to suppress the presentation of the origination number
of calls regardless of how the call comes into the system.
The following sytax is used: MapAll<num>=#<port><num>
Example: The following example shows an appropriate configuration. With this entry, all calls beginning
MapAll0=40DATA:0 DATA
...
MapAll9=40DATA:9 DATA
MapAll0=|40DF:0<<24
...
MapAll9=|40DF:9<<24
Restrict40=In
MapAllIn=10
[Voip:DF]
VoipDirection=IO
...
VoipCompression=g711a g729 trp t38
...
[Voip:DATA]
VoipDirection=Out
...
VoipCompression=trp
VoipECE=No
...
...
InsertCLIR=On
...
Restrict9=OK 01
Restrict|9=OK 01
Restrict90=FAIL 01
...
MapInOK00491555=2200491555
MapInFAIL=&aa
...
C O N V E R S I O N O F C A L L N U MB E R S
CHAPT E R 8
128
with 00491555 are sent to the port with the address 22 and the presentation of the number is
restricted:
8 . 4 . 3 S E T T I N G C L I P
Setting an exclamation point (!) in front of a call number makes it possible to force the presentation of the origi-
nation number of calls regardless of how the call comes into the system.
The following sytax is used: MapAll<num>=!<port><num>
Example: The following example shows an appropriate configuration. With this entry, all calls beginning
with 004930 are sent to the port with the address 9 and the presentation of the origination num-
ber is allowed.:
8 . 5 C O N V E R S I O N O F C A L L N U MB E R S
The conversion of call numbers makes it possible, for example, to implement number portability or to redirect calls
when the user can be reached at another number. In the following mapping command, the call number
015550123456 is changed to 015559876543 (MapAll...=9..):
Example 1
Example 2 presents an alternative, in which the routing file is searched through again after conversion of the call
number to determine the route for the prefix 01555. Please bear in mind that you can configure a maximum of
5000 mapping entries with no more than 11 digits in the first part of the command and 19 in the second.
Example 2
MapAll00491555=#2200491555
MapAll004930=!9004930
...
MapAll015550123456=9015559876543
...
MapAll015550123451=$Reception
MapAllReception=015559876543
S E T T I N G N U MB E R T Y P E I N O A D / D A D
CHAPT E R 8
129
8 . 6 S E T T I N G N U MB E R TY P E I N OA D / DA D
In some cases it may be necessary to set a specific number type for the OAD or DAD. There are different methods
for the various interfaces. The following number types can be set:
OAD
Use the following entry to set a specific number type in the OAD:
Restrict<port><num>=<type> 15
For the national and international types, remove the 0(s) at the beginning of the number:
Restrict<port>0=n 15
Restrict<port>00=i 15
Example: In the following example, the bit is set in the callers origination number for a call via BRI con-
troller 01:
Example:
You can set a u (unknown type of number) in the Restrict entry to change transmission of the national/inter-
national bit to 0 or 00 at the beginning of the OAD. As in a mapping entry, the national/international bit will always
appear left of the equal sign as 0 or 00.
Restrict<port>0=u0 15
Restrict<port>00=u00 15
In the following example, the area code 030 with a 0 at the beginning of the OAD of the PBXs extension is set as
a digit and transmitted along with the number:
Table 8.89 Number Types
Type Definition
u Unknown
s Subscriber number
n National number
i International number
Restrict90=n 15
Restrict900=i 15
Restrict10555=u030555 15
Restrict entries are handled from general to specific from top to bottom.
i i
S E T T I N G T H E S C R E E N I N G I N D I C A T O R
CHAPT E R 8
130
DAD
Enter one of the four specific number types in the DAD as follows:
MapAll<num>=<port><type><num>
In the case of a VoIP controller, enter the following:
MapAll<num>=<port><voip profile>:<type><num>
The number type will then be defined at the port. For the national and international types, remove the 0(s) at the
beginning of the number:
Example: In the following example, the international bit is set for all calls to Italy (0039) and the number
is transmitted with 39. For the area code 012, the national bit is set and the number is trans-
mitted with 12:
8 . 7 S E T T I N G T H E S C R E E N I N G I N D I C A T O R
You can set the screening indicator to define whether the calling-party number sent is specified as user
provided verified and passed or network provided:
User provided verified and passed: v
Example: In the following Restrict example, the calling party number sent is specified as user
provided verified and passed:
Network provided: p
Example: In the following Restrict example, the calling party number sent is specified as network
provided:
If you also want to define a number type (see Chapter 8.6 ), it must appear in front of the screening indicator:
Example: In the following Restrict example, the screening indicator is specified as network
provided, and the number type is international:
MapAll0039=40iG1:i39 VOICE
MapAll012=40iG1:n12 VOICE
Restrict10=v 15
Restrict10=p 15
Restrict10=ip 15
Please bear in mind that this entry will not work if you set a minus sign (-) behind
VoipOad=<num>.
i i
S E T T I N G A D E F A U L T O A D
CHAPT E R 8
131
General Example
Example: In the following example, a 1:1 routing entry for the individual BRI controllers to VoIP appears in
addition to the international flag from BRI to VoIP. A placeholder routing entry is used (bla or
blu), in which the BRI ports are directly assigned to a mapping. Traffic at BRI port 9 is sent di-
rectly to VoIP port 40 with the VoIP profile iG1. Traffic from BRI port 10 is sent to VoIP port 40
with the profile iG2:
8 . 8 S E T T I N G A D E F A U L T OA D
Use the Restrict command to set a default origination number (*<oad> 15) when the OAD is restricted
(<num>):
Restrict<port><oad>=*<num> 15
Example: In the following example, 12345 replaces the original OAD. When the destination number begins
with 030, the call is sent through controller 10:
Use the entry Restrict<port><oad>=<num> 15 if digits at the beginning of the OAD are the only ones to
be restricted.
Example: In the following example, the digits 004930 are replaced with 030 followed by the remaining
digits. The destination number begins with 030 and is sent through port 10.
8 . 9 S E T T I N G S E N D I N G C O MP L E T E B Y T E I N S E T U P
In some cases the ISDN or H323 peer system may require this byte for routing, or the byte may disrupt signaling.
Setting Sending Complete
The following entry ensures that the Setup includes a Sending Complete:
restrict9=bla
restrict900=i 15
restrict10=blu
restrict1000=i 15
MapAllbla00=40iG1:i
MapAllblu00=40iG2:i
The Restrict entries for the individual ports must appear in the following order:
placeholder, OAD international flag, DAD routing with international flag.
Restrict9=*12345 15
MapAll030=10030
Restrict9004930=030 15
MapAll030=10030
i i
MI S C E L L A N E O U S R O U T I N G ME T H O D S
CHAPT E R 8
132
MapAll<direct>=)<num>
The ) causes inclusion of Sending Complete in the ISDN Setup or in the H323 Setup.
Example: In the following example, all calls beginning with 0 are sent with a Setup Complete to controller
9:
Removing Sending Complete
The following entry ensures that the Setup never includes a Sending Complete:
MapAll<direct>=(<num>
The ( causes removal of Sending Complete in the ISDN Setup or in the H323 Setup.
Example: In the following example, all calls beginning with 0 are sent without a Setup Complete to VoIP
controller 40. The VoIP profile is DF:
8 . 1 0 MI S C E L L A N E O U S R O U T I N G ME T H O D S
In the following scenarios it may occur that some call numbers must be routed with differing lengths or that some
call numbers may require additional number conversion:
Calls without a destination number
Connection to a PBX with an extension prefix
Routing based on the length of the destination number
8 . 1 0 . 1 R O U T I N G C A L L S WI T H O U T A D E S T I N A T I O N N U MB E R
Enter the following configuration in the route.cfg if the VoIPBOX BRI must route calls that come in without a
destination number:
Restrict<port>=<pl>
MapAll<pl><num>=<port><num>
MapAll<pl>=<port>
Incoming calls from the configured port will be assigned a placeholder and then all calls beginning with the place-
holder will be routed to the placeholders placeholders mapping.
Example: In the following example, all calls from controller 9 are routed to controller 10, regardless of
whether a destination number appears in the setup:
MapAll0=)90
MapAll0=(40DF:0
Restrict9=pl
MapAllpl=10
CHAPT E R 8
133
8 . 1 0 . 2 R O U T I N G C A L L S B A S E D O N E X I S T E N C E O F D E S T I N A T I O N N U M-
B E R
To route calls with a DAD differently from those without a DAD, you must activate the block feature in the
pabx.cfg and restart the system:
Block=1
Set all other parameters in the route.cfg. First define the port from which the incoming calls are to be routed.
Incoming calls from the configured port will be assigned a placeholder and then digit collection will occur for all
calls beginning with the placeholder. The $ in the mapping entry, followed by the defined placeholder (MMM), caus-
es a second search of the routing file when the number is complete:
DTMFWaitDial=<sec>
Restrict<port>=<pl>
MapAll<pl>=|$MMM<<98
The second routing-file search is based on the routing entry with the leading placeholder (MMM):
MapAllMMM<digits>=<dest><digits>
Example: In the following example, digit collection is activated for all calls that come into port 9. Calls with
the destination number 2222 are sent to the VoIP controller with the profile DF and the destina-
tion number is replaced with the SIP account Betty. Calls with the num-ber 3333 are sent to
VoIP with the SIP account Al. All other calls with a destination number are sent to controller 10.
Calls without a destination number are sent to the number 12345 at port 10:
8 . 1 0 . 3 C H A N G I N G C A U S E VA L U E S
It is possible to group cause values together into a single defined cause value so that rejected calls can be handled
in a specified manner by the PBX sending the call to the VoIPBOX BRI. The following cause value groups can be
defined in the pabx.cfg:
Group 0 Cause Values
All connections that are rejected with a group 0 cause value (0x80-0x8f) can be mapped to a single cause value
by entering TranslateG0Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.
DTMFWaitDial=5
Restrict9=pl
MapAllpl=|$MMM<<98
MapAllMMM2222=40DF:Betty
MapAllMMM3333=40DF:Al
MapAllMMM0=100
MapAllMMM1=101
MapAllMMM2=102
MapAllMMM3=103
MapAllMMM4=104
MapAllMMM5=105
MapAllMMM6=106
MapAllMMM7=107
MapAllMMM8=108
MapAllMMM9=109
MapAllMMM=1012345
CHAPT E R 8
134
All connections that are rejected with a group 1 cause value (0x90-0x9f) can be mapped to a single cause value
All connections that are rejected with a group 2 cause value (0xa0-0xaf) can be mapped to a single cause value
All connections that are rejected with a group 3 cause value (0xb0-0xbf) can be mapped to a single cause value
Translating Individual Cause Values
The following parameter allows you to translate any of these cause values to any other one:
Translate<cause>=<cause>. The values entered must be in hexadecimal notation between 00 and 7f.
Translating SIP Causes to ISDN and Vice Versa
You can define a specific translation from SIP responses (4xx - 6xx) to ISDN cause values and vice versa. If nothing
is set, the translation occurs as described in draft-kotar-sipping-dss1-sip-iw-01.txt
Use the following parameter to translate a cause from ISDN to a specific SIP response:
SipCause<ISDN cause>=<SIP Response>
Repeat the entry to initiate an additional translation.
Use the following paramter to translate a cause from SIP to ISDN:
SipEvent<SIP Response>=<ISDN Cause>
The following range of values applies:
400<= <SIP Cause> <=699 (defined in RFC 3261)
0<= <ISDN Cause> <=127 (DSS1 decimal cause number)
C A R R I E R S E L E C T I O N
CHAPT E R 9
135
9 L EAST COST ROUT I NG
VoIPBOX BRIes are connected between the customers private branch exchange (PBX) and the public telephone
network (PSTN) and/or VoIP. The customer saves connection charges and can effortlessly and automatically con-
nect to the carrier as needed using one of the following six ISDN routing methods:
Carrier selection
Dedicated lines
Direct line access with subaddressing
Direct line access with DTMF
Callback with DTMF
This manual contains information only on carrier selection. If you would like to configure any other variation, please
contact TELES or refer to the TELES Infrastructure Systems Manual Version 4.5, Chapter 3.
Calls are routed transparently for the PBX and its users. VoIPBOX BRIes can generate charges and route calls using
alternate settings in case of network failures.
The following additional services are supported by this feature package:
Generation of charges
Time-controlled configuration
Alternative routing
9 . 1 C A R R I E R S E L E C T I O N
Carrier selection is currently one of the most commonly used routing methods supported by the VoIPBOX BRI. In
the VoIPBOX BRI, this routing process also includes calls into the GSM network or through a VoIP network. That
means the system is a full-fledged second generation LCR.
9 . 1 . 1 R O U T I N G E N T R I E S
Use the MapAll command to route calls using Carrier Selection.
a) Use the following syntax for connections routed via the provider:
MapAll<AreaCode>=9<CarrierSelection><AreaCode>
where <AreaCode> is the number or number range to be routed and <CarrierSelection> is the
access number required to reach the providers network.
b) For unrouted connections (placed via the public telephone network), use:
MapAll<AreaCode>=9<AreaCode>
c) To block undesired carrier selection prefixes use:
MapAll<CarrierSelection>=&91;(Busy signal)
In the following example, calls to international destinations are terminated through the VoIP interface. The profile
names iG1 and iG2 in the routing entries refer to different VoIP carriers. All other national long distance and local
calls are routed through an alternative carrier (01019). All calls from the PSTN or VoIP to the PBX are put through
transparently.
A L T E R N A T I V E R O U T I N G S E T T I N G S
CHAPT E R 9
136
Example:
9 . 2 A L T E R N A T I V E R O U T I N G S E T T I N G S
Alternative routing refers to the ability to establish connections using a different (alternative) network in case of
provider failure (e.g. the VoIP connection has been disrupted). Alternative routing ensures uninterrupted operation
of the attached PBX. In such cases, connections are often made via the public network using the Redirect com-
mand:
MapAll<num>=<port><num>
Redirect3<port><num>=<placeholder>
MapAll<placeholder>=<alt port><num>
Example:
MapAll001=40iG1:001
MapAll0044=40iG2:0044
...
MapAll01=90101901
MapAll02=90101902
...
MapAll09=90101909
MapAll1=9010191
MapAll2=9010192
...
MapAll9=9010199
Restrict9=10
Restrict40=10
Be sure to enter phone numbers in the routing file in ascending order.
MapAll001=40iG1:001
Redirect340iG1:=A
MapAllA=9
i i
C H A R G E MO D E L S
CHAPT E R 9
137
9 . 3 C H A R GE MO D E L S
VoIPBOX BRIes can either generate charge information or transmit received charges from the public or corporate
networks to the attached PBX. Charge simulation on the VoIPBOX BRI is achieved using variables, which ensure a
great degree of flexibility for the implementation of many different charge models including:
Charge units per time unit
Flat rate (initial charge without time interval)
Initial charge plus time interval
Initial charge plus time interval after delay
Time interval and/or flat rate plus received charges
Received charges only or no charge information
Initial toll-free period with retroactive charge generation afterwards
Price-per-minute (with whole second accuracy)
In this chapter, unit means that charge information is transmitted as a whole-numbered value, and currency
means that the charge information is sent as a currency amount (e.g. EUR 3.45). The charge impulse generation
options can be set for each mapping by adding charge-specific arguments to the MapAll commands as shown
below. The use of each variable is explained in Table 9.90.
MapAllsrc=dst mode time start/wait and
MapCallBackOutprovsrc=dst mode time start/wait.
Any external charges can be added to the generated charges by adding 128 to the start value. (The value range
for the initial unit level is still set from 0 to 127). The maximum supported number of units per connection is 32767
units.
Table 9.90 Charge Variables
Variable Purpose
time Determines the length of each time interval (how long each unit lasts). The value is entered in
seconds and hundredths or thousandths of a second (the maximum value accepted is 655.35
seconds, 65.535 if thousandths are entered). If time is set to zero or not present, no charges
are generated. External charge information is passed through if received.
start Sets the initial unit level. Enter a value between 0 and 127 whole units. If you want to use a
flat rate, set the desired number of units here and set the wait to 255 to turn off the time in-
terval.
wait Determines the delay after which charge generation begins. Once this time has elapsed, charge
impulses are sent in the interval determined with time. Enter a value between 0 and 254 sec-
onds. 255 deactivates the charge pulse. In this case, the time variable is ignored.
Charges can be generated only for NT ports.
i i
G E N E R A T I N G C H A R G E S WI T H T H E V O I P B O X B R I
CHAPT E R 9
138
Additional adjustments may be made to allow for the implementation of new charge models.
When charge information is sent as Currency, values can be expressed in thousandths for greater precision
in charge calculation.
For the internal Layer 3 protocols, charges can be specified to the third decimal place (thousandth) using the
/Value option (Example: /Value:1.056). In this fashion, charges can be generated for units of currency
requiring accuracy to the third decimal place or for fractions such as tenths of a cent. This allows for greater
flexibility in the transmission of charges to terminal devices. In order to make use of this option, connected
devices must support AOC-D Currency.
A multiplication factor can be specified for received or generated charges.
During the charge generation process, each charge unit is multiplied by a preset factor. This factor appears in
the mapping entry after the time and start/wait variables (MapAllsrc=dst mode time start/wait*factor).
Each unit, for example, can be converted to 12 cents. The following example illustrates the use of this feature:
In the above example, all received charge units are multiplied by 12 and passed on. If AOC-Currency is set on
the internal port, each unit appears as 12 cents.
The multiplication factor is also used to implement two new charge models:
If the factor value exceeds 128, this marks the use of an initial toll-free phase followed by retroactive
charge generation.
If the multiplication factor is set to 255, a minute price is used in place of the time variable.
These charge models are explained on page 9-139.
9 . 4 G E N E R A T I N G C H A R GE S WI T H T H E VO I P B OX B R I
To generate charges for the attached PBX, add the charge variables described in Table 9.90 to the MapAll com-
mands according to the necessities of the corporate network environment.
Example 1 MapAll0172=9123450172 1.65 131/0
(time=1.65, start=131, wait=0)
In the mapping example above, 3 initial tariff units (131-128) are transmitted upon connection
and a new unit is generated every 1.65 seconds and transmitted the next full second. Charges
received from the public network for the connection to the corporate network dial-in node are
added and transmitted (because 128 has been added to the start variables value).
Example 2 MapAll0172=9123450172 1.65 131/10
(time=1.65, start=131, wait=10)
Upon connection establishment, 3 initial tariff units (131-128) are transmitted. Then a 10-second
delay (wait=10) elapses before charge impulses are generated according to the time variable (a
new unit is generated every 1.65 seconds and transmitted the next full second). Charges received
from the public network for the connection to the corporate network dial-in node are added and
transmitted (because 128 has been added to the start variables value).
...
MapAll1=91 1 128/255*12
...
CHAPT E R 9
139
New charge models can be implemented by taking advantage of the multiplication factor in conjunction with the
time and start/wait variables.
Retroactive charge generation after initial toll-free period
The charge generation process has been expanded to allow for the implementation of this new charge model.
In this scenario, an initial period is free of charge, but after this period charges are calculated for the entire
CHAPT E R 9
140
call. For example: the first minute is free, but as soon as the second minute begins, charges are incurred for
the first minute as well.
The multiplication factor is set to a base value of 128. If the value exceeds this base, the remaining value rep-
resents the number of units charged with each time interval. The following configuration generates one unit
(129-128) per minute (time=60 seconds) retroactively after the first minute (wait=60 sec.):
Price per minute
A price per minute charge model can be configured to assign one thousandth (1000) of a currency unit (0.001
or 10 of a cent) to each charge unit.in one of two ways:
either the attached PBX supports Advice of Charges as Currency
or if not, the PBX can be configured to assign one thousandth (1000) of a currency unit (0.001 or
10 of a cent) to each charge unit.
This model does not always guarantee whole second accuracy (depending on the rates), but it is significantly
more precise than the standard charge generation method.
If the attached PBX supports Advice of Charges as Currency, include the following line in the VoIPBOX BRIs
pabx.cfg:
If the PBX does not support this AOC model, but allows for the assignment of one thousandth (1000) of a
currency unit (0.001 or 10 of a cent) for each charge unit, the above entry need not be present. The config-
uration entries must make use of the multiplication factor for a single unit as shown below:
If the minute price does not allow generated charges to fit evenly into a second (such as 20 cents per minute
or 0.33 cents per second), the system can be configured to generate 10 points every 3 seconds (0.01 or 1
cent):
The points method allows for a more precise calculation of smaller intervals.
...
MapAll030=901019030 60 0/60*129
...
If thousandths are defined, a maximum value of 65.535 is possible. If tenths are de-
fined, a maximum value of 6553.5 is possible.
...
Controller01=10 NT DSS1 UNIT: VALUE:0.001
...
...
MapAll02=90103002 1.00 0/0*4 ; each second costs 0.004 (0.24 / minute)
MapAll09=90108809 1.00 0/0*5 ; each second costs 0.005 (0.30 / minute)
...
...
MapAll02=90101302 3.00 0/0*10 ; 3 seconds cost 0.01 (0.20 / minute)
MapAll09=90105009 2.00 0/0*3 ; 2 seconds cost 0.003 (0.09 / minute)
...
i i
CHAPT E R 9
141
The price per minute can also be explicitly specified in each routing entry by setting the multiplication factor
to 255, to signalize to the system that a minute price is being used instead of the interval usually specified with
the time variable. The attached PBX must support Advice of Charges as Currency, and the appropriate settings
must be made in the VoIPBOX BRIs pabx.cfg as described on page 9-140. The examples below show sam-
ple entries with rates of 18 and 9 cents per minute:
and
If greater precision is desired (1000 of a currency unit $0.001 or 10 of a cent), use settings such as the
following:
and
...
MapAll902=0101302 0.18 0/0*255 ; 0.18 / minute
MapAll909=0105009 0.09 0/0*255 ; 0.09 / minute
...
...
...
...
MapAll902=0101302 1.80 0/0*255 ; 0.18 / minute
MapAll909=0105009 0.90 0/0*255 ; 0.09 / minute
...
...
...
A S R C A L C U L A T I O N A N D R E S E T T I N G S T A T I S T I C V A L U E S
CHAPT E R 10
142
10 ONL I NE TRAF F I C MONI T OR
The Online Traffic Monitor allows you to collect and monitor statistics and call detail records (CDRs). The following
functions are possible with this feature package:
ASR calculation
Generation of CDRs
Generation of online CDRs using e-mail
1 0 . 1 A S R C A L C U L A T I O N A N D R E S E T T I N G S T A T I S T I C VA L U E S
When this function is configured in the pabx.cfg file, statistical values, such as the number of minutes, number
of calls, ASR, etc., are calculated for the entire system at a defined time. These statistics are then copied into a
specified file and reset at 0.
This information can also be sent to an e-mail recipient. The following syntax must be used:
StatisticTime=<file> <hh:mm> <day> @<account>
Example: In the following example, the systems statistic values are saved daily into the file stati.log
and sent to an e-mail account.
Example: If ?? appears instead of a specified hour, the ASR is written into the stati.log file once every
hour. The values are reset to zero in the twenty-third hour:
Example: The next example shows how the statistics appear in the file into which they are copied. The fol-
lowing information is listed in the following order: day and time of the entry, followed by the sys-
tem name. Calls: connected calls followed by the total number of calls in parentheses. The total
number of minutes terminated by the system, followed by the ASR1 value, the external ASR for
the traffic source (ext) and the internal ASR for the VoIPBOX BRI (int). These values can differ if
a significant number of calls cannot be routed through the VoIPBOX BRI or an insuffficient num-
ber of channels is available for a prefix. Finally, the average call duration (ACD) appears in the
entry:
StatisticTimeReset=<file> <hh:mm> <day> performs the same function as the StatisticTime
parameter, but also resets the counters (A-F).
Bear in mind that the mail server must be configured in the [Mail] section of the
pabx.cfg, as described in Chapter 5.2.2 .
StatisticTime=stati.log 00:00 11111111 @<account>
StatisticTimeReset=stati.log ??:00
26.10.05-00:00:00,BoIPBOX: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% - ASR(ext): 65.12% -
ASR(int): 65.30% - ACD: 144.63s
i i
G E N E R A T I N G A N D R E T R I E V I N G C D R S
CHAPT E R 10
143
Example: In the following example, the systems statistic values are saved on the 15th of every month into
the file reset.log.
1 0 . 2 G E N E R A T I N G A N D R E T R I E V I N G C D R S
With the Log and RrufLog commands, you save CDRs and unconnected calls in the VoIPBOX BRI.
For these parameters (Log and RrufLog), a folder and file name must always be specified after the equal sign.
The function is not active (no data is recorded) until a file name is specified.
Example:
The service indicator listed in the call log and missed calls list describes the type of connection as a four digit hexa-
decimal number. The coding is conducted according to the 1TR6 standard. A few frequently used values are listed
below:
StatisticTimeReset=reset.log 00:00 15.
It is not possible to configure both StatisticTimeReset and StatisticTime.
ASR values reset to 0 when the SIM card is changed using the GATE Manager.
Log=/boot/cdr.log
RRufLog=/boot/failed.log
With recording of files, system maintenance increases. You have to be sure to down-
load or delete files and ensure that there is enough disk space left on the hard drive.
Table 10.91 1TR6 Service Indicators
Service Indicator Definition
0101 ISDN-telephony 3.1 kHz
0102 analog telephony
0103 ISDN-telephony 7 kHz
0200 Fax group 2
0202 Fax group 3
0203 Data via modem
i i
i i
CHAPT E R 10
144
For detailed information on how to automatically divide the files (e.g. on a daily basis), please refer to the
Chapter 5.2.1.2 .
1 0 . 2 . 1 C A L L L O G
The following entry in the pabx.cfg configuration file activates the capability to generate CDRs in the
VoIPBOX BRI:
Log=/boot/cdr.log
The cdr.log file is stored in the data directory. New entries are always added to the end of the file. The file is
open only during editing.
Each line represents an outgoing call:
DD.MM.YY-hh:mm:ss[Start],DD.MM.YY-hh:mm:ss[End],src,dst,service,dur,cause,charge_publine,[charge_sys]
The charge is specified in units. The service indicator listed will be one of the values shown on Table 10.91. The
example below shows a sample log file.
0400 Telefax group 4
0500 SMS or BTX (64 kbps)
07 Bit rate adaptation
1001 Video telephone audio 3.1 kHz
1002 Video telephone audio 7 kHz
1003 Video telephone video
DD Day hh Hour src source/extension dur duration
MM Month mm Minute dst destination cause reason for teardown
YY Year ss Seconds service service indicator charge_publine from the public line
charge_sys generated by the system
28.01.05-19:38:51,28.01.05-19:44:51,10611,9010193333333,0101,360,90,10
28.01.05-19:43:55,28.01.05-19:44:55,10610,26212015551111111,0101,60,90,3
28.01.05-19:32:54,28.01.05-19:44:55,10612,40iG2:004498989898,0101,721,90,15
28.01.05-19:41:34,28.01.05-19:45:34,10616,9010190123456,0101,240,90,4
28.01.05-19:44:19,28.01.05-19:45:49,10615,26212015553333333,0101,90,90,5
28.01.05-19:44:58,28.01.05-19:45:58,10610,26213015562222222,0101,60,90,3
28.01.05-19:46:01,28.01.05-19:47:12,10610,9010194444444,0101,71,90,5
28.01.05-19:46:18,28.01.05-19:47:48,10615,40iG1:001232323232323,0101,90,90,4
28.01.05-19:47:03,28.01.05-19:48:07,10610,9010195555555,0101,64,90,4
28.01.05-19:48:07,28.01.05-19:49:07,10610,9010190306666666,0101,60,90,3
Table 10.91 1TR6 Service Indicators (continued)
Service Indicator Definition
CHAPT E R 10
145
To differentiate between ports with the same number in the CDRs, a specific node number must be defined. You
can expand the subscriber configuration line with the keyword NODE[<no.>] for this purpose. <no.> can
be a string of between 1 and 15 characters:
Subscriber<xx>=... NODE[<num>]
The following entry shows the pabx.cfg configuration file changed according to the formula:
Example: In the following CDR entry, <num> consists of a four-digit number (0000) that is included in the
CDR.
To generate a VoIP-call CDR entry that includes IP addresses for the remote devices signaling and voice data, audio
codec and frame size, the entry VoipIpLogging=Yes must be included in the VoIP profile.
The following entry shows the route.cfg configuration file changed according to the formula:
Example: The following CDR entry includes IP addresses for signaling and voice data , audio codec and
frame size.
In the case of CDR entries for DLA/Callback calls, the beginning and ending times for the first call leg is always
used as the call time. The call time in seconds appears first for the first leg, followed by a slash and the connection
time for the second leg.
Example:
1 0 . 2 . 2 MI S S E D C A L L S L I S T
All incoming calls that are not connected can be recorded in a list to facilitate return calls. Recording is activated
using the RRufLog=<name> entry in the pabx.cfg. Specify a file name, e.g. RRufLog=failed.log. Once
this setting is made, recording begins at once.
A new line of the following format is created for each incoming call that is not accepted:
...
Subscriber00=TRANSPARENT ROUTER ALARM NODE[0000]
...
29.08.05-09:45:24,29.08.05-09:46:33,923456789,[0000:01]01771111111,0101,69,0
[Voip=Default]
VoipDirection=IO
VoipMaxChan=30
VoipSignalling=0
VoipTxM=4
VoipIPLogging=Yes
21.08.07-11:54:09,21.08.07-11:54:14,40501,172.20.25.210:172.20.25.210,G729,20,0101,5,90,0
20.10.05-15:27:36,20.10.05-15:30:36,2621201555555555,DLA1234567890,0101,180/168,10,0
G E N E R A T I N G O N L I N E C D R S V I A E - MA I L
CHAPT E R 10
146
DD.MM.YY-hh:mm:ss,src,dst,cause,dur,att
The reason the connection could not be established is specified using DSS1 codes:
91 (user busy)
ff call not answered (disconnected by calling party)
When callback with DTMF is configured and no connection is established to the B subscriber, an entry recording
the A subscribers connection time is generated in the failed.log file:
The CDR contains the IP addresses for signaling and voice data. The first IP address is the signaling address and
the second one is the RTP address.The IMSI is written behind the IP addresses if the keyword IMSI is defined in
the pabx.cfg:
Example:
In the case of missed-call entries for DLA/Callback calls, dur is the connection time for the first leg.
Example:
1 0 . 3 G E N E R A T I N G O N L I N E C D R S V I A E - MA I L
With an appropriate configuration, you can send corresponding CDRs of outgoing and incoming calls as e-mail.
Bear in mind that the mail server must be configured in the [Mail] section of the pabx.cfg, as described in
Chapter 5.2.2 . The sender is given as cdr and the systems name appears in the subject box. The text box con-
tains the CDR information according to the format for the entry in Log=/data/cdr.log @<account>
DD Day hh Hour src source/extension cause reason for tear down
MM Month mm Minute dst destination dur duration of call attempt
YY Year ss Seconds service service indicator att number of attempts
16.01.05-13:58:52,9030399281679,10111,0101,ff,0,1
16.01.05-14:04:06,9030399281679,10111,0101,91,0,1
16.01.05-14:04:15,9,10111,0101,91,0,1
16.01.05-14:04:39,9030399281679,10111,0101,ff,0,1
16.01.05-14:04:50,903039904983,100,0101,ff,0,1
16.01.05-14:05:02,9030399281679,10111,0101,ff,0,1
16.01.05-14:05:03,9,100,0101,ff,0,1
16.01.05-14:05:14,903039904983,100,0101,91,0,1
20.04.05-16:21:10,[4545]981776,2->10200,0101,ff,0,1
20.04.05-16:21:20,[4545]981776,1->10120,0101,ff,0,1
20.02.05-10:47:52,[0004:01]00491721234567,[0005:01]DLA0307654321,0101,ff,34,1
12.05.05-10:25:51,40,991783,172.20.25.110:172.20.25.110,0101,ff,8,1
20.10.05-15:00:06,9004930555555,DLA262121111111,0101,92,24,1
G E N E R A T I N G O N L I N E C D R S V I A E - MA I L
CHAPT E R 10
147
@<domain>. A space must appear between cdr.log and @<account>; @<domain> is optional. You can
also send CDR entries via e-mail to an e-mail recipient. Each CDR entry generated is sent as e-mail. The following
entry in the configuration file activates this function:
...
Log=/data/cdr.log @<e-mail account>@<domain>
...
C A L L C O N N E C T O R A N D C A L L B A C K S E R V E R
CHAPT E R 11
148
11 DL A/ CAL L BACK SERVI CES
This chapter describes money-saving features that expand the functionality of your VoIPBOX BRI to include callback
capability and DTMF services. It is particularly useful for companies with employees who travel often, because it
eliminates expensive roaming fees.
1 1 . 1 C A L L C O N N E C T O R A N D C A L L B A C K S E R V E R
Various intelligent solutions as a call server are possible. The most important scenarios and properties are described
here. The scenarios can also be combined to suit your needs.
Special announcement
DLA with DTMF
DLA with fixed destination number
Callback with DTMF for the second leg number (known OAD or fixed callback number)
Callback with DTMF and OAD as callback number
Callback with DTMF and pre-configured callback number
Callback for a fixed second leg
DLA with DTMF and PIN for the first leg and callback for the second leg
Using a PIN in front of the call number
Callback via SMS
Callback via HTTP
Numbers transmitted using DTMF tones can be ended by entering a # sign. Otherwise, a 5-second timer is set, after
which DTMF transmission will automatically end.

Activating DTMF Tone Recognition
The VoIPBOX BRI can recognize DTMF tones and initiate calls with these tones. In the pabx.cfg, enter a virtual
DTMF controller, as described in Table 5.20. The corresponding Subscriber entry contains the options:
TRANSPARENT ROUTER CHMAX[2]
The 2 refers to the maximum number of simultaneous channels used for DTMF recognition.
Example:
CDR entries for calls routed as Callback with DTMF include the connection times for
the A and B subscribers. The times are separated by a slash (/). If no connection is
established to the B subscriber, an entry recording the A subscribers connection time
is generated in the failed.log file.
...
Controller09 = 41 DTMF
...
Subscriber09 = TRANSPARENT ROUTER CHMAX[2]
...
i i
CHAPT E R 11
149
1 1 . 1 . 1 S P E C I A L A N N O U N C E ME N T
An announcement can be played immediately after the connection has been established. The announcement can
be defined in the virtual DTMF controllers Subscriber line using the following entry:
In the pabx.cfg file:
DTMF[<sec>,/<dir>/<file>]
<sec> refers to the maximum number of seconds that may pass before the next DTMF tone is entered, <dir>
refers to the directory, in which the announcement file is saved. boot or data are possible. The file extension
must be 711.
Example: In this example, a maximum of 2 channels can recognize DTMF tones and change them into di-
aling data. The announcement is named DTMF.711 and is saved in the boot directory:
1 1 . 1 . 2 D L A WI T H D T MF
The user dials a number in the system that is connected with the DTMF platform. She then enters the number with
which she would like to be connected.
Make the following entries in pabx.cfg to connect a call directly:
MapAll<number>=<DTMFport>DTMF
MapAllDLA=<port>
Example: In the following example, the call from the number 123 is connected to the DTMF platform and
the call that comes in as DTMF tones is directed to the VoIP port and the VoIP profile DF:
The VoIPBOX BRI must be restarted to activate this configuration.
The files sound format must be PCM!
Subscriber09 = TRANSPARENT ROUTER DTMF[30,/boot/DTMF.711] CHMAX[2]
MapAll123=41DTMF
MapAllDLA=40DF:
This feature applies only for calls that come from GSM or VoIP. Analog calls are not
supported.
i i
i i
i i
CHAPT E R 11
150
1 1 . 1 . 3 D L A WI T H F I X E D D E S T I N A T I O N N U MB E R
The user dials a number in the system that is connected directly with a fixed external number (e.g. international
subsidiary number). Make the following entry in the route.cfg:
MapAll<num>=<port><fixed num>
Example: In the following example, the call comes into the number 123456 and is connected to the num-
ber 004311111 at the VoIP port and the VoIP profile DF:
1 1 . 1 . 4 C A L L B A C K WI T H D T MF A N D OA D A S C A L L B A C K N U MB E R
The user calls a number that is defined so that the user will be called back based on his OAD. An alerting occurs.
The user hangs up and is called back. After the user has taken the call, the destination number is entered using
DTMF tones. When he has finished dialing, the connection to the destination number is established.
The following entries in route.cfg will initiate callback to the calling partys number:
MapAllDTMF=<DTMFport>DTMF
MapAllDLA=<port>
MapAll<number>=CALLB
MapAllCB=<port>
Example: In this example, the call with the number 123 is connected with the OAD and the number that
comes in as DTMF is directed to the VoIP port and the VoIP profile DF:
MapAll123456=40DF:004311111
Callback is not possible for VoIP calls.
MapAllDTMF=41DTMF
MapAll123=CALLB
MapAllCB=10
MapAllDLA=40DF:
Please configure only one ISDN port 10, as callback to ISDN occurs only through the
first configured port number (in the example :10).
i i
i i
CHAPT E R 11
151
1 1 . 1 . 5 C A L L B A C K WI T H D T MF A N D P R E C O N F I G U R E D C A L L B A C K N U M-
B E R
The user calls a predefined number that is mapped to a defined callback number. An alerting occurs. The user
hangs up and is called back at a fixed number. After the user has accepted the call, she must enter the destination
number via DTMF. The connection is set up when she finishes dialing.
Make the following entries in route.cfg to initiate callback to a fixed number:
MapAllDLA=<port>
MapAll<number>=CALL<callbacknumber>
Example: In the following example, the call with the number 123 is connected with the number 03012345.
The number that comes in as DTMF is directed to the VoIP port and the VoIP profile DF:
1 1 . 1 . 6 C A L L B A C K T O OA D A N D F I X E D S E C O N D L E G
The user calls a predefined number in the system. An alerting occurs. The user hangs up and is called back based
on her OAD. After the user accepts the call, she is connected to a fixed, preconfigured number (e.g. operator or
corporate central office.
Make the following entries in route.cfg:
MapAllDTMF=<port><num>
MapAll<num>=CALLB
MapAllCB=<port>
Example: In the following example, the caller dials 123456 and her OAD is called back through the ISDN
port 10. She is then connected with 501 via the VoIP port and the VoIP profile DF.
MapAllDTMF=41DTMF
MAPAllDLA=40DF:
MapAll123=CALL903012345
MapAllDTMF=40DF:501
MAPAll123456=CALLB
MapAllCB=10
i i
i i
CHAPT E R 11
152
1 1 . 1 . 7 D L A WI T H D T MF A N D P I N F O R F I R S T L E G A N D C A L L B A C K F O R
S E C O N D L E G
The user dials a number in the system that is connected to the DTMF platform. He then enters a predefined PIN
that maps him to a predefined fixed number that is to be called back. He then hangs up. After he takes the callback,
he can enter the second leg number using DTMF tones.
Make the following entries in route.cfg:
MapAll<num>=<DTMFport>DTMF VOICE
MapAllDLA<num>=CALL<num> VOICE
MapAllDLA=<port> VOICE
Example: The number 123456 is dialed and the PIN 123# is entered. The call is then connected to the num-
ber 004930123456. The destination number can now be transmitted through the VoIP port and
the VoIP profile DF using DTMF tones:
1 1 . 1 . 8 U S I N G A P I N I N F R O N T O F T H E C A L L N U MB E R
To prevent abuse, the following entry can be made to configure a PIN in front of the actual call number:
MapAllDLA=$PIN
MapAllPIN<pin>=<port>
Example: In the following example, the DTMF tones are analyzed, whereby the first 4 (1111) corresponds
with the PIN. The call to subscriber B is initiated when the PIN has been entered correctly. All
other DTMF tones are directed to the VoIP port and the VoIP profile DF:
Please configure only one ISDN port 10, as callback to ISDN occurs only through the
first configured port number (in the example :10).
MapAllDTMF=41DTMF
MAPAll123456=41DTMF VOICE
MapAllDLA123=CALL9004930123456 VOICE
MapAllDLA=40DF: VOICE
The user must enter a # following the PIN. Otherwise the callback to the predefined
number will not occur. This feature applies only for calls that come from GSM or VoIP.
Analog calls are not supported.
MapAllDLA=$PIN
MapAllPIN1111=40DF:
i i
i i
S I G N A L I N G P A R A ME T E R S
CHAPT E R 12
153
12 ADDI T I ONAL VOI P PARAMET ERS
You can enter the following additional parameters in the route.cfg to adjust the configuration for improved
communication with the VoIP peer.
1 2 . 1 S I G N A L I N G PA R A ME T E R S
Table 12.92 Customized Parameters: Protocol-Independent VoIP Signaling
Protocol-Independent VoIP Signaling Parameters
VoipDad=<num>
The digits/numbers defined here will appear in front of the original DAD. If the parameter is to be valid in
only one direction, you must set another profile without this parameter for the other direction.
VoipOad=<num>
The digits/numbers defined here will be transmitted in front of the original OAD. If a minus (-) is entered, the
original OAD will not appear. Only the digits entered in front of the minus sign will be displayed. If the pa-
rameter is to be valid in only one direction, you must set another profile without this parameter for the other
direction.
To limit this feature to OADs consisting of a certain number of digits, enter a !, followed by the number of
digits, at the end of the entry. In the following example, the digits 567 will appear only if the OAD has at
least 6 digits:
EXAMPLE: VoipOad=567!6
To modify the original OAD, enter randomx, whereby x represents a number of random digits that will ap-
pear in the OAD.
EXAMPLE: VoipOad=567random2-
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.
VoipComprMaster=<mode>
This parameter defines which side the first matching codec comes from:
Yes: Default. Priority is determined by the order of the systems parameter list.
No: Priority is determined by the peer.
CHAPT E R 12
154
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 partys presentation or screen-
ing 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. Transmis-
sion of the OAD can occur in the P-asserted header.
VoipSignalCLIR=<string>
When the configured string appears at the beginning of 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.
VoipIgnoreDADType=<mode>
Enter yes to change the DAD type to unknown, e.g. from international. The type is lost, e.g. the leading 00
bit is removed. Default no.
VoipSuppressInbandInfoAvailableIndicatorInCallProceeding=<mode>
Enter yes to send or receive the Progress Indicator in the Q.931 Call Proceeding message. Default no.
VoipG72616PayloadType=<num>
Changes the SIP payload type for G.726 16 b/s. Default is 35. A common value is 102.
VoipG72624PayloadType=<num>
Changes the SIP payload type for G.726 24 b/s. Default is 36. A common value is 99.
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.
VoipDataBypassPayloadType=<num>
Defines the payload type for the RTP packets when the call is sent as a data call. Default 96.
VoipMinDigitOnTime=<ms>
Defines the minimum length of DTMF tones, to ensure DTMF tone detection. Default 0.
VoipMinInterDigitTime=<ms>
Sets a time interval for DTMF tone detection. Default 0.
Table 12.92 Customized Parameters: Protocol-Independent VoIP Signaling (continued)
Protocol-Independent VoIP Signaling Parameters
CHAPT E R 12
155
Table 12.93 Customized Parameters: H.323 Signaling
H.323 Signaling Parameters
VoipService=0x<service indicator>
This parameter sets the barrier capability. For example, it can be used for calls coming from VoIP with the
barrier 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:
VoipService=0x101
VoipMapAddressType=<mode>
For calls from PSTN to VoIP only. Enter yes to change the 00 at the beginning of a number to international
and 0 to national.
VoipSetupAck=<int>
1=setup acknowledge is transmitted; 0= setup acknowledge is not transmitted; 2 (default) =transmitted
with H.323 information.
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.
VoipCanOverlapSend=<mode>
Enter off to deactivate overlap sending during setup (default on).
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.
CHAPT E R 12
156
Table 12.94 Customized Parameters: SIP Signaling
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 origina-
tion address (e.g. from ISDN) followed by an @ sign will automatically be set at the beginning.
VoipOwnDisplay=<string>
The entry is sent as Display Name in the From Field in SIP transmissions. The keyword MSN causes the calling
telephones MSN to be transmitted as Display Name.
Example: From: "John" <sip:493011111@teles.de>
VoipContact=<account@domain>
Used for the Contact field in Sip-Invite and Sip-Response messages.
VoipP-Preferred-Identity=<string>
Sets the P-Preferred-Identity field in the SIP invite message. The following settings are possible toward 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
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
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
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.
CHAPT E R 12
157
VoipDadSource=<int>
SIP only: defines the field from which field the called party number coming from SIP is to be taken:
0 = URL
1 = To: field
2 = Remote-Party-ID with party = called
VoipUseMaxPTime=<mode>
SIP only. Enter yes to set the field mptime (max packet time) with the values set in VoipTxm (ptime).
Default no.
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.
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.
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 digets come from ISDN/POTS with
overlap sending. When this parameter is active, VoipPrack is automatically set to yes. Default is no.
VoipSdpProxy=<mode>
SIP only. Enter yes to activate proxy mode for SDP signaling for SIP to SIP calls. The parameters for RTP sig-
naling will be forwarded from one leg to the next and RTP is not handled by the system. 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
URIs available digits or to the invite messages To field. No (default) means that the digit contents of the
SubsequentNumber field will be used.
Table 12.94 Customized Parameters: SIP Signaling (continued)
L O C A T I O N S E R V E R P A R A ME T E R S
CHAPT E R 12
158
1 2 . 2 L O C A T I O N S E R V E R PA R A ME T E R S
The following parameters can be used in the VoIP profile when the SIP agent wants to register with the
VoIPBOX BRI.
Example: The following example creates an account for a user agent with the username 130 and password
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.
VoipDelayDisc=<mode>
Yes (default) delays confirmation transmission during call teardown. That means the release tone is audible
when the peer tears down the call.
NOTE: For versions 13.0c or lower: To improve ASR, we recommend that you set this parameter to Yes if
you use the parameter VoipMaxChan.
Table 12.95 Customized Parameters: Location Server
Location Server Parameters
VoipOwnUser=<string>
Defines the username the agent uses to register.
VoipOwnPwd=<string>
Defines the password the agent uses to register.
VoipExpires=<sec>
Defines the maximum number of seconds the agents registration applies (default 3600).
VoipAuth=<mode>
Defines the authentication procedure www (default) or proxy.
Table 12.94 Customized Parameters: SIP Signaling (continued)
L O C A T I O N S E R V E R P A R A ME T E R S
CHAPT E R 12
159
test130. Authentication occurs with the procedure www:
MapAll130=40U1:130
[Voip:U1]
VoipDirection=IO
VoipOwnUser=130
VoipOwnPwd=test130
VoipExpires=300
VoipAuth=www
VoipCompression=g711a g711u g729 g729a g729b g729ab
VoipSilenceSuppression=no
VoipSignalling=1
VoipMaxChan=8
VoipTxM=2
VoipDtmfTransport=0
R O U T I N G P A R A ME T E R S
CHAPT E R 12
160
1 2 . 3 R O U T I N G PA R A ME T E R S
Table 12.96 Customized Parameters: VoIP Routing
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 num-
bers (e.g. other codec, WaitForConnect, etc.). 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 total 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 coma 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.
VoipUseIpStack=<mode>
Enter Yes to facilitate direct use of an xDSL or dial-up connection if the corresponding profile is defined.
Default is No.
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.
VoipEnumDomain=<string>
Use this parameter to modify the domain name for the enum query (default is e164.arpa).
VoipUseStun=<mode>
Enter yes (default yes) to use the STUN values for the VoIP profile.
VoIPOwnIpAddress=<ip addr>
If the system is behind a NAT firewall that does not translate H.323 or SIP, the NAT firewalls public IP address
is transmitted as own IP address in the H.323 or SIP protocol stack (not the private IP address). In this case,
the public IP address must be defined. Bear in mind that the NAT firewall transmits the ports for signaling
and voice data to the VoIPBOX BRIs private IP address.
Q U A L I T Y P A R A ME T E R S
CHAPT E R 12
161
1 2 . 4 Q U A L I T Y PA R A ME T E R S
Table 12.97 Customized Parameters: VoIP Quality
VoIP Quality Parameters
VoipSilenceSuppression=<mode>
Activates silence suppression (see Table 5.26).
VoipBandwidthRestriction=<mode>
Enter Yes to include the VoIP profile in traffic shaping. Default is No. For a description of the functionality,
please refer to VoipMaximumBandwidth in Table 5.22.
VoipMediaWaitForConnect=<mode>
This parameter allows you to influence the systems behavior in relation to voice channel negotiation (RTP
stream).
The following settings are possible:
No (default): RTP data is transmitted immediately after negotiation for RTP. SIP: Early Media is activated; SDP
is sent with 183 or 180.
Yes: The negotiation of RTP data is sent only after the connection has been established. SIP: SDP is sent only
with 200 and ack.
Tone: The VoIP peer or the connected PBX requires generation of inband signaling tones (alert, busy, re-
lease).
NOTE: If Tone is entered, the tones are not played in the direction of the PBX if RTP is already exchanged
before connect (inband is switched through).
Bear in mind that the parameter SWITCH in the VoIP controllers Subscriber line must be removed if the
tones are played for the PBX.
If Tone is entered and the tones are played to VoIP, the VoIP media channel cannot be released following
an ISDN call disconnect as long as the tones are being transmitted. This can result in CDR errors on the peer
side.
VoipRtpTos=<num>
Enter a value between 0 and 255 to set the TOS (type of service) field in the RTP packet IP header. Possible
values are described in Table 12.98. If your IP network uses diferentiated services, you can also define the
DSCP (differentiated services codepoint) for the RTP packets. The DSCP is the first six bits in the TOS octet.
NOTE: VoipUseIpStack must be 0 (default).
VoipRtcpTos=<num>
Enter a value between 0 and 255 to set the TOS (type of service) field in the RTCP packet IP header. Possible
values are described in Table 12.98. If your IP network uses diferentiated services, you can also define the
DSCP (differentiated services codepoint) for the RTCP packets. The DSCP is the first six bits in the TOS octet.
NOTE: VoipUseIpStack must be 0 (default).
CHAPT E R 12
162
VoipPCMPacketInterval=<int>
This parameter changes the default interval for PCM codecs (G.711, G.726). That means the VoipTxm fac-
tor is muliplied using this interval:
0 = 10ms (default))
1 = 5 ms
2 = 10 ms
3 = 20 ms
VoipCallGroup=<name>
All outgoing VoIP calls for VoIP profiles with the same VoipCallGroup name are distributed cyclically to
these profiles.
VoipOverflow=<name>
When the value entered in VoipMaxChan is reached, all overflow calls will be sent to the profile defined
here. An alternative VoIP profile can also be used if the default profile can no longer be used as a result of
poor quality.
VoipDJBufMinDelay=<count>
Enter a value in milliseconds (0-320) to set a minimum jitter buffer limit (default 35). For fax transmission
(t.38) it is fixed to 200ms.
NOTE: VoipDJBufMaxDelay must be greater than VoipDJBufMinDelay.
VoipDJBufMaxDelay=<count>
Enter a value in milliseconds (0-320) to set a maximum jitter buffer limit (default 150). For fax transmission
(t.38) it is fixed to 200ms.
NOTE: VoipDJBufMaxDelay must be greater than VoipDJBufMinDelay.
VoipDJBufOptFactor=<count>
Enter a value between 0 and 13 to set the balance between low frame erasure rates and low delay (default
7).
VoipConnBrokenTimeout=<sec>
An entry is generated in the protocol.log file and the connection is terminated after a connection bro-
ken exists for the number of seconds entered (default 90). If 0 is entered, no entry will be generated and the
connection will not be terminated.
VoipTcpKeepAlive=<mode>
Enter yes (default) to send the RoundTripDelayRequest message every 10 seconds (necessary for
long calls with firewalls using TCP aging).
VoipIntrastar=<mode>
Enter Yes to activate the IntraSTAR feature. When the IP connection results in poor quality, an ISDN call is
sent to the peer and the voice data is automatically transmitted via ISDN.
Table 12.97 Customized Parameters: VoIP Quality (continued)
CHAPT E R 12
163
VoipBrokenDetectionTimeout=<ms>
When this parameter is set, the system recognizes an interruption in the transmission of RTP/RTCP data in
the VoIP connection following the set number of milliseconds. This parameter is necessary to set up an
IntraSTAR call immediately when the IP connection is disrupted. Bear in mind that
VoipSilenceSuppression=No must appear in the VoIP profile. For a description of IntraSTAR, see
Chapter 8.1 . For an example, see Chapter 6.7 .
VoipAutoRtpAddr=<mode>
Some application scenarios require automatic RTP IP address and port recognition for VoIP calls, for example
if a firewall or NAT changes the IP address of incoming RTP data. Enter Yes to activate automatic recognition
(default No).
CHAPT E R 12
164
VoipAGC=<x y z>
This parameter allows automatic gain control of input signals from PSTN or IP. Enabling this feature compen-
sates for near-far gain differences:
x - direction (0 for signals from TDM, 1 for signals from IP)
y - gain slope (controls gain changing ratio in -dBm/sec, values 0 to 31, default 0)
z - target energy (determines attempted signal energy value in -dBm, values 0 to 63, default 19
Gain Slope:
0 - 00.25dB
1 - 00.50dB
2 - 00.75dB
3 - 01.00dB
4 - 01.25dB
5 - 01.50dB
6 - 01.75dB
7 - 02.00dB
8 - 02.50dB
9 - 03.00dB
10 - 03.50dB
11 - 04.00dB
12 - 04.50dB
13 - 05.00dB
14 - 05.50dB
15 - 06.00dB
16 - 07.00dB
17 - 08.00dB
18 - 09.00dB
19 - 10.00dB
20 - 11.00dB
21 - 12.00dB
22 - 13.00dB
23 - 14.00dB
24 - 15.00dB
25 - 20.00dB
26 - 25.00dB
27 - 30.00dB
28 - 35.00dB
29 - 40.00dB
30 - 50.00dB
31 - 70.00dB
CHAPT E R 12
165
VoipVoiceVolume=<num>
The volume of VoIP calls coming from the Ethernet. The range is 0-63. The default value of 32 is 0 dB.
VoipInputGain=<num>
The volume of VoIP calls coming from ISDN,POTS or mobile. The range is 0-63. The default value of 32 is 0 dB.
CHAPT E R 12
166
VoipQualityCheck=<type minsamples limit recovertime>
type
Enter one of the following: ASR1, ASR2, RoundTripDelay, Jitter or FractionLost
When type is ASR1 or ASR2:
minsamples
Minimum number of calls for which ASR shall be calculated with:
limit
A value between 0 and 100
recovertime
Seconds to block the profile.
When type is RoundTripDelay:
minsamples
Minimum number of seconds RTD must be above:
limit
The highest acceptable value for RTD (in milliseconds)
recovertime
When type is Jitter:
minsamples
Minimum number of seconds jitter must be above:
limit
The highest acceptable value for jitter (in milliseconds)
recovertime
When type is FractionLost:
minsamples
Minimum number of seconds FL must be above:
limit
The highest acceptable value for FL (percentage between o and 100)
recovertime
Seconds to block the profile
NOTE: If you base VoipQualityCheck on the ASR values: During setup, calls are calculated as not con-
nected, which lowers the number of connected calls.
Example: If minsamples is set at 20, with a limit of 80%, 4 calls in the setup phase will lower the ASR
of the previous 20 calls to 80% and the profile will be blocked.
VoipECE=<mode>
Enter yes (default) to set ITU G. 168 echo cancellation. Enter no to disable echo cancellation.
CHAPT E R 12
167
The following specifications for Quality of Service correspond with RFC791 and RFC1349.
=<ms>
This parameter defines the required tail length for echo cancelation. The following values in ms are possible:
32
64 (default)
128
VoipT301=<sec>
An outgoing VoIP calls will be canceled in the state of Alerting (for H323) or Ringing (for SIP) if the number
of seconds entered has passed and there is no response from the IP or VoIP carrier.
VoipT303=<sec>
If this parameter is entered in a SIP profile, transmission of the INVITE is canceled after the number of seconds
entered has passed. The call can then be redirected, for example to PSTN. This improves the reliability of the
system when an IP or VoIP carriers service fails.
EXAMPLE:
Redirect340DF:=A
MapAllA=9
[Voip:DF]
.....
VoipT303=5
VoipT304=<sec>
An outgoing VoIP calls will be canceled in the state of Setup Acknowledge (for H323) or Trying (for SIP) if
the number of seconds entered has passed and there is no response from the IP or VoIP carrier.
VoipT310=<sec>
An outgoing VoIP calls will be canceled in the state of Call Proceeding (for H323) or Session Progress (for
SIP) if the number of seconds entered has passed and there is no response from the IP or VoIP carrier.
Table 12.98 Quality of Service Values
Bit
Distribution
0 1 2 3 4 5 6 7
Precedence TOS MBZ
Bit Description
0-2 Precedence
3 TOS: 0=normal delay, 1=low delay
4 TOS: 0=normal throughput, 1=high throughput
5 TOS: 0=normal reliability, 1=high reliability
C O MP R E S S I O N P A R A ME T E R S
CHAPT E R 12
168
1 2 . 5 C O MP R E S S I O N PA R A ME T E R S
The following parameters are for RTP multiplexing, which aggregates RTP packets (voice user data) for individual
VoIP calls into a packet. The header (for Ethernet, IP, UDP and RTP) is sent only once for all calls instead of for each
individual call. The relationship between header and payload benefits the payload when several calls occur simul-
taneously. This compression does not result in any loss in voice quality.
This feature is possible with a Teles peer and requires the following entries in the VoIP profile:
6 TOS: 0=normal service, 1=minimize monetary cost
7 MBZ: must be 0 (currently not used)
Precedence Description
111 Network control
110 Internetwork control
101 CRITIC/ECP
100 Flash override
011 Flash
010 Immediate
001 Priority
000 Routine
Table 12.99 Customized Parameters: VoIP Compression
VoIP Compression Parameters
VoipAggRemoteRtpPort=<port>
Enter the port for the VoIP peer that is the first RTP port. The next port is always the corresponding RTCP
port. The port that is two numbers higher will be used for the next VoIP channel. Default 29000.
VoipAggRemoteDataPort=<port>
VoipAggRemoteDataPort=29500
Enter the port for the VoIP peer that is used for aggregated packets (compressed data). Default: 29500.
VoipAggOwnDataPort=<port>
VoipAggOwnDataPort=29500
Enter the own port number used for aggregated packets. Default: 29500.
VoipAggRemoteRtpPortSpacing=<count>
Defines the space between the ports used for the peers individual RTP streams (default 2).
Table 12.98 Quality of Service Values (continued)
F A X / MO D E M P A R A ME T E R S
CHAPT E R 12
169
1 2 . 6 F A X / MO D E M PA R A ME T E R S
Table 12.100 Customized Parameters: VoIP Fax
VoIP Fax/Modem Parameters
VoipFaxTransport=<int>
Enter 2 and signaling will switch to G.711a (framesize 40ms) when the peer cannot handle fax transmission
with T.38. The codec will change when the system detects a fax or modem connection on the channel. 0 =
disabled (default); 1 = relay. T.38 is always used.
NOTE: Bear in mind that if T.38 is defined in the VoipCompression= line of the VoIP profile, the system
will switch only when it detects a modem connection. Fax calls will still be transmitted using T.38.
VoipFaxBypassPayloadType=<num>
Defined the payload type for a faxs RTP packets when T.38 is not used (default 102).
VoipFaxMaxRate=<num>
If the peer does not support auto negotiation or has a fixed transmission rate, you can define the fixed rate:
0 - 2400 Bit/sec
1 - 4800
2 - 7200
3 - 9600
4 - 12000
5 - 14400 (default)
EXAMPLE:
VoipFaxMaxRate=5
VoipFaxECM=<mode>
You can use this parameter to disable the error correction mode for fax transmission: yes=enabled (default),
no=disabled.
VoipFaxProtocol=<int>
Defines the protocol used:
0 = TCP
1 = FRF.11
2 = UDP, datarate management 1
3 = UDP, datarate management 2 (default)
VoipT38ErrorCorrectionMode=<int>
Sets the error-correction mode:
0 = Redundancy (default)
1 = Forward error correction
F A X / MO D E M P A R A ME T E R S
CHAPT E R 12
170
VoipT38CtrlDataRedundancy=<int>
Defines the redundancy level for control packets:
0 = Disable (default)
1-7 = Sets level
VoipT38ImageDataRedundancy=<int>
Defines the redundancy level for fax content:
0 = Disable (default)
1-3 = Sets level
The following parameters are responsible to set the modem transport method if a modem connection is detected.
VoipV21Transport=<mode>
0=disabled (must be set to 0).
0=disabled, 2=bypass (default).
0=disabled, 2=bypass (default).
0=disabled, 1=relay (default), 2=bypass .
0=disabled, 1=fallback to v32, 2= bypass (default).
Table 12.100 Customized Parameters: VoIP Fax (continued)
VoIP Fax/Modem Parameters
D T MF P A R A ME T E R S
CHAPT E R 12
171
1 2 . 7 D T MF PA R A ME T E R S
Table 12.101 Customized Parameters: VoIP DTMF
VoIP DTMF Parameters
VoipIBSDetectDir=<int>
Enter 1 and DTMF tones (and all other inband signaling) will be detected from the Ethernet side. Enter 0 for
DTMF tones to be detected from the PCM side (default). DTMF tones from the Ethernet side are transmitted
to the host as ISDN dialing information only if 1 is entered. In this case, VoipDtmfTransport should be
1 or 3.
VoipDtmfTransport=<int>
0 (H323) = DTMF relayed with H.225 signaling information.
0 (SIP) = DTMF relayed with SIP INFO.
1 = DTMF and MF taken from audio stream and relayed to remote.
2 (default) = DTMF and MF kept in audio stream and not relayed.
3 = DTMF and MF taken from audio stream and relayed to remote as per RFC2833.
4 (SIP only) = SIP INFO messages will be relayed as DTMF and MF.
VoipDtmfFallback=<int>
If VoipDtmfTransport=3 is set and the peer does not support DTMF transmission according to RFC
2833, the following settings apply:
2 = automatic fallback to inband
0 = automatic fallback to signaling messages (default)
VoipRFC2833PayloadType=<num>
This parameter changes the DTMF payload type. The default value is 96, a common value is 101.
VoipMinDigitOnTime=<ms>
Defines the minimum length of DTMF tones, to ensure DTMF tone detection. Default 0.
VoipMinInterDigitTime=<ms>
Sets a time interval for DTMF tone detection. Default 0.
O V E R V I E W
CHAPT E R 13
172
13 OPT I ONAL F UNCT I ON MODUL ES
This chapter contains a description of modules that expand the functionality of the VoIPBOX BRI, such as:
HTTP User Interface
iPBX
SNMP agent
DNS forwarder
ipupdate - DynDNS client
Since these features are only required in individual cases, they are not part of the default software packet. They
can be installed as stand-alone modules for the desired function. The description of the functionality of individual
modules appears in their respective chapters.
1 3 . 1 O V E R V I E W
The modules can be downloaded using FTP. The access data for each module is as follows:
Http User Interface
ftp://195.4.12.80
user: httpd
password: httpd
iPBX
ftp://195.4.12.80
user: ipbx
password: ipbx
DNS Forwarder
ftp://195.4.12.80
user: dnsmasq
password: dnsmasq
snmp agent
ftp://195.4.12.80
user: snmp
password: snmp
ipupdate
ftp://195.4.12.80
user: ipupdate
password: ipupdate
Install the respective software package on the VoIPBOX BRI using TELES.GATE Manager. For a description of how
to update the software, please refer to Chapter 7.3 . Make sure the modules file ending is correct before instal-
lation. The number in the file ending shows the starting order of the modules. Do NOT change this number if it is
0! All other modules can simply be numbered in ascending order.
For instance, the ending for the optional function module will be tz2 or higher:
tz2
tz3
H T T P U S E R I N T E R F A C E
CHAPT E R 13
173
Following completion of transmission, you must adjust the modules configuration and restart the VoIPBOX BRI.
Once you have restarted the system, you can use the required features.
1 3 . 2 H T T P U S E R I N T E R F A C E
The HTTP user interface is a user-friendly tool that can be used by carriers, administrators and individual users to
configure the VoIPBOX BRI. For a detailed description of the HTTP user interface, please see Chapter 4.11.2 .
1 3 . 3 I P B X
The iPBX is a soft PBX that runs as an add-on application on TELES CPE devices. These include VoIPBOX BRIes (BRI
or analog). It is used to connect local IP telephones and soft phones, as well as traditional line-based PBX exten-
sions and telephones. The connection to the public telephone network can occur via VoIP, through the traditional
PSTN network, or a combination of both. Both analog and ISDN (BRI) lines can be connected as PSTN. Connection
to the carrier can occur using SIP, H.323, or a combination of both. Multiple VoIP destinations can be can be
mapped through the routing process. The iPBX can be used to add local or remote IP extensions (work@home) to
an existing PBX without requiring changes to the existing PBX, or you can implement the iPBX to completely re-
place your old PBX. For further information, please refer to the iPBX Systems Manual, which can also be found on
the FTP server.
Features
Caller ID
Call forward/transfer
Call parking/retrieve
Conference calling
DND (Do Not Disturb)
Music on hold
Direct inward dial access
Direct outward dial
Different dial plans
Hunt groups
Push to talk
Dial by name
Fax support
Voicemail
IVR
1 3 . 4 S N MP A GE N T
This module allows you to connect the systems and their functions to an SNMP-based network monitoring system.
With this module, SNMP requests are answered and alarm messages (E.g. Layer 1 errors on E1 lines) and error
recovery messages are sent via SNMP trap.
D N S F O R WA R D E R
CHAPT E R 13
174
Traps are generated for all line or mobile ports. The running number in the trap corresponds with the port. The
module also monitors whether the voice codec chips are functioning correctly.
The traps for the IP interfaces are also generated in ascending order according to the following list:
Bear in mind that the keyword ALARM must be entered in the appropriate BRI ports Subscriber line in the
pabx.cfg. The MIBs (Management Information Bases) are included on the product CD in the folder MIB. The
module name snmpd.tz0 must have the ending tz0!
The following settings are possible in the section [snmpd]:
1 3 . 5 D N S F O R WA R D E R
With this module, the system can function as a DNS server for the clients in the local network. The system in the
local network sent the DNS query to the VoIPBOX BRI, which forwards the queries to a known DNS server address
if no valid entry for the query is known.
The advantage is that the clients always enter the VoIPBOX BRIs address as DNS server address, so that no public
DNS server address is required. The VoIPBOX BRI functions in this scenario as a router.
Table 13.102 Traps for IP Interfaces
Trap Number Interface
0 Ethernet 1
1 Ethernet 2
2 Loopback
3 xppp= (if used)
4 pppoe= (if used)
Table 13.103 Settings in the Section [snmpd]
Parameter Definition
Port=<port> Defines the target port for the trap server (default 161).
TrapServer=<ip addr> Enter the SNMP trap servers IP address. Example for listing more than
one:
TrapServer=192.168.0.10 192.168.0.12
Community=<password> Enter a password for a community (group). The default password is
public.
I P U P D A T E - D Y N D N S C L I E N T
CHAPT E R 13
175
Of course, the DNS servers address can also be transmitted to the clients using the integrated DHCP server. If the
VoIPBOX BRI is used as a DSL router or if it sets up a dial-up connection, no entry is required in the pabx.cfg
for the parameter NameServer. The DNS servers address that is negotiated through this connection will be
used.
1 3 . 6 I P U P D A T E - D Y N D N S C L I E N T
This function allows you to assign a defined hostname to an IP address that changes dynamically. That means that
you can always reach a device or service through the public IP network, even if, for example, it is a common DSL
connection with dynamic IP address allocation. Several providers support this service.
Make the following entries in the systems ip.cfg, in the [DynDNS] section:
Table 13.104 pabx.cfg: DynDNS
DynDNS Parameters
service=<type>
Specifies which provider is used. The following providers are supported:
dhs
dyndns
dyndns-static
dyns
ezip
easydns
easydns-partner
gnudip
heipv6tb
hn
pgpow
ods
tzo
zoneedit
http://www.dhs.org
http://www.dyndns.org
http://www.dyns.cx
http://www.ez-ip.net
http:/www.easydns.com
http://www.gnudip.cheapnet.net
http://www.hn.org
http:www.justlinux.com
http://ods.org
http://www.tzo.com
http://zoneedit.com
user=<username:password>
Defines the username and password for the DNS service provider.
host=<domain_name_of_dns_service>
Enter the domain name that is used.
interface=<If>
Defines the interface to be used. Possible entries are emac0, emac1, pppoe0. The dynamic IP address for
this interface is transmitted to the service provider.
I P U P D A T E - D Y N D N S C L I E N T
CHAPT E R 13
176
Example: In the following example, the DynDNS service is used and the domain name is
host.domain.de; the username is user and the password is pwd. The VoIPBOX BRI works
as DSL router and the dynamically allocated IP address of the PPPoE interface is used:
Included in the possible uses for this feature is remote access to the VoIPBOX BRI when the IP connection does not
have a fixed IP address. In this case, you can access the system, for example with the TELES.GATE Manager, if the
host name is used in the Remote Number dialog. Example entry in the Remote Number dialog:
IP:host.domain.de
max-interval=<sec>
Defines the value in seconds in which actualization of the name in the DNS database must occur. 2073600
seconds (24 days) is the default value. The shortest interval allowed is 60 seconds. Bear in mind that this
setting may cause the provider to block the domain name, since multiple registrations in short intervals are
often not allowed. You must clear this with your provider.
[DynDNS]
service=dyndns
user=user:pwd
host=host.domain.de
interface=pppoe0
max-interval=2073600
Table 13.104 pabx.cfg: DynDNS (continued)
DynDNS Parameters
TELES AG
Communication Systems Division
Ernst-Reuter-Platz 8
10587 Berlin, Germany
Phone: +49 30 399 28-00
Fax: +49 30 399 28-01
E-mail: sales@teles.com
http://www.teles.com/tcs/

TELES VoIPBOX BRI 14.0

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TELES VoIPBOX BRI 14.0

Caricato da

Copyright:

Formati disponibili

Software version 14.

Potrebbero piacerti anche