Teles Informationstechnologien GSM32VOIPUS GSM Gateway User Manual TELES iGATE

Teles AG Informationstechnologien GSM Gateway TELES iGATE

User Manual

Software version 15.0iGATE
TABLE OF CONTENTS2Chapter 1 – About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81.1 organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Chapter 2 – Safety and Security Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.1 Safety Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 FCC / Industry Canada Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Tips for EMC Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 Servicing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5.1 Replacing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5.2 Protecting the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.6 CDR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.7 Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Chapter 3 – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.1 What’s New in Version 15.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3 How iGATE Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.4 Supported Implementation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Chapter 4 – Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234.1 Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2 Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.3 Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.4 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.4.1 Ethernet Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.4.2 PRI Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26TELES to TBR12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Former TELES Assignment to Current TELES Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.4.3 BRI Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.4.4 Antenna Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.4.5 SIM Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27The SIM-Card Carrier Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.5 Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.6 Hardware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.7 Startup with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.7.1 Installing Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.7.2 Configuration with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.8 Startup via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.9 Startup via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36table of contents
TABLE OF CONTENTS34.10 Self Provisioning with NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.11 LED Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.11.1 iLCR Base Board PRI Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.11.2 iGATE 4 Mobile Board SIM-Card LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.12 Remote Access and Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.12.1 GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.12.2 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.12.3 FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.12.4 Setting a Password for Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Chapter 5 – Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445.1 Configuration File ip.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.1.1 System Section Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.1.2 Ethernet Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.1.3 Bridge Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1.4 NAT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1.5 PPPoE Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1.6 Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1.7 Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.1.8 DHCP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1.9 PPP Configuration for ISDN and CDMA Dial-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.1.10 VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.1.11 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Active Ethernet Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Integrated DSL-Router Scenario for VoIP Traffic with an Active DHCP Server and Firewall. . . . . . . . 58VLAN Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.2 Configuration File pabx.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.2.1 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Life Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Night Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Global Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.2.2 SMTP-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.2.3 Number Portability Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.2.4 SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.2.5 Time-Controlled Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.2.6 .CASR2 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.3 Configuration File route.cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
TABLE OF CONTENTS45.3.1 Entries in the [System] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Restrict. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Setting the Time-Controlled Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865.3.2 VoIP Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.3.3 Gatekeeper Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915.3.4 Registrar Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925.3.5 Radius Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Chapter 6 – Routing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .966.1 iGATE Integration in a Carrier Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.2 iGATE Integration with SIM-Card Switching in an H.323 Carrier Network . . . . . . . . . . . . . . . . . 976.3 iGATE as a Second-Generation LCR with VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Chapter 7 – Mobile Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1017.1 Connection to a vGATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017.2 Module Distribution of Various Mobile Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017.3 Network-Specific Mobile Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037.3.1 Using a Fixed Mobile Port Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037.3.2 Using the LAIN as the Mobile Port Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047.3.3 Fixed LAIN for a Mobile Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057.4 Incoming Voice Calls from Mobile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057.5 Blocking Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057.6 Setting Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067.7 Automatic SIM Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077.7.1 Switching SIMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.7.2 Cyclical SIM Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.7.3 Immediate SIM Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.7.4 Count Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.8 Defining Time Limits for Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.9 Pause between Two Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107.10 Time-Controlled SIM Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107.11 Mobile-User PBX Callback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.12 Optional Mobile Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137.13 Deactivating Mobile ReRouting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.14 Disconnecting Calls After Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177.15 Checking Ports/Mobile Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177.16 Recharging Prepaid SIMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
TABLE OF CONTENTS57.16.1 Recharge Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Checking the Active SIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Addressing SIMs Using Port- and Controller-Specific Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Blocking the Port Containing the Recharging SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197.16.2 Recharging Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Direct Recharging via Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Indirect Recharging via GATE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207.16.3 Prepaid Account Status Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Direct Account-Status Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Indirect Account-Status Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Saving /Forwarding the Account Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277.17 Defining Special Characters for Voice Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Chapter 8 – Signaling and Routing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1288.1 Digit Collection (Enblock/Overlap Receiving). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288.2 Rejecting Data Calls and Specified Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288.2.1 Blacklist Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288.2.2 Whitelist Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298.2.3 Rejecting Calls with ISDN Bearer Capability Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298.2.4 Specific Routing of Data Calls via VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308.3 CLIP and CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308.3.1 Routing CLIP and CLIR Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308.4 Routing Calls without CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318.4.1 Setting CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318.4.2 Setting CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318.5 Conversion of Call Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328.6 Setting Number Type in OAD/DAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328.7 Setting the Screening Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348.8 Setting a Default OAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358.9 Setting or Removing Sending Complete Byte in Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358.10 Excluding Prefixes from vGATE Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.10.1 Exclusion from SIM Daily Call Attempts Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.10.2 Exclusion from SIM Minutes Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.11 Miscellaneous Routing Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.11.1 Routing Calls without a Destination Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.11.2 Routing Calls Based on an Extension Prefix or on the Length of the Destination Number . . . . . . . 1378.12 Changing Cause Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Chapter 9 – Additional VoIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1399.1 Signaling Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399.2 Registrar Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469.3 Routing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
TABLE OF CONTENTS69.4 Quality Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489.5 Compression Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559.6 Fax/Modem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569.7 DTMF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Chapter 10 – System Maintenance and Software Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15910.1 Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15910.2 Status and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15910.3 Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16610.4 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16810.4.1 ISDN Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17010.4.2 GSM/CDMA/UMTS Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17010.4.3 VoIP Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Interface IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Internal Protocol Interface (to ISDN, Mobile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183H.245 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185RAS (Registration, Admission, Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190ENUM Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19510.4.4 Remote Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19910.4.5 SMTP Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20010.4.6 Number Portability Trace Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20310.4.7 DTMF Tone Trace Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Chapter 11 – Feature Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20711.1 Activating the License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20711.2 DLA/Callback Server Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20811.2.1 Call Connector and Callback Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Special Announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209DLA with DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209DLA with Fixed Destination Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Callback with DTMF and OAD as Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Callback with DTMF and Pre-Configured Callback Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Callback to OAD and Fixed Second Leg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211DLA with DTMF and PIN for First Leg and Callback for Second Leg . . . . . . . . . . . . . . . . . . . . . . . 211Using a PIN in Front of the Call Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Callback via SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21211.3 Least Cost Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21311.3.1 Carrier Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Routing Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21311.3.2 Alternative Routing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21411.3.3 Charge Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
TABLE OF CONTENTS711.3.4 Generating Charges with the iGATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21611.4 Online Traffic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21911.4.1 ASR Calculation and Resetting Statistic Values and Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Saving and Sending Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Saving Statistics and Resetting Statistic Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Resetting Statistic Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22111.4.2 Generating and Retrieving CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Missed Calls List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Sending CDRs via E-Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22711.5 SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22811.5.1 Sending SMS via E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22811.5.2 Receiving SMS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229SMS to E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229SMS to SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229SMS to File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23011.5.3 Incoming USSD (Unstructured Supplementary Services Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23011.5.4 Sending Messages via E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23011.5.5 Setting Up Connections via E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23111.5.6 Displaying Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23111.5.7 Sending Automatic SMS for Unconnected Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23211.6 Ported Number Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23211.6.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23311.6.2 Routing and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Chapter 12 – Optional Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23512.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23512.2 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23612.3 SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23612.4 DNS Forwarder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23712.5 ipupdate - DynDNS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
ABOUT THIS MANUALCHAPTER 18iGATE 15.0. Revised: 2009.1 ABOUT THIS MANUALCongratulations on the purchase of your new iGATE! This manual is set up to guide you through the step-by-stepinstallation of your iGATE, so that you can follow it through from the front to the back. Quick-installation instruc-tions appear in Chapter 4.7, “Startup with Quickstart” >. Make sure you familiarize yourself thoroughly with the safety and security precautions detailed in Chapter 2 >before you begin to install your iGATE. TELES is not liable for any damage or injury resulting from a failure to followthese safety and security instructions!1.1 ORGANIZATIONThis manual is organized into the following chapters.Chapter 1, “About this Manual” > introduces the iGATE Systems Manual and how it is set up.Chapter 2, “Safety and Security Precautions” > contains information about security issues relevant to con-nection with the IP network.Chapter 3, “Overview” > briefly describes the iGATE and its implementation scenarios.Chapter 4, “Installation” > contains information on how to connect and configure the system so that it is ready for operation.Chapter 5, “Configuration Files” > describes the iGATE’s individual configuration files and parameters.Chapter 6, “Routing Examples” > contains useful examples and descriptions of scenario-based configura-tions in the route.cfg.Chapter 7, “Mobile Configuration Options” > describes mobile configuration entries.Chapter 8, “Signaling and Routing Features” > describes configuration settings in the route.cfg used for adjusting PRI signaling and customizing the configuration for specific scenarios.Chapter 9, “Additional VoIP Parameters” > contains additional configuration entries to fine-tune commu-nication with the VoIP peer.Chapter 10, “System Maintenance and Software Update” > describes system messages that are saved in the protocol file, as well as trace options.Chapter 11, “Feature Packages” > contains a description of options that expand the iGATE’s functionality.Chapter 12, “Optional Function Modules” > contains a description of expansion modules.1.2 CONVENTIONSThis 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 8 > – cross-references can be accessed in the PDF files by a single mouse click. Configuration data or extracts are written in single-column tables with a gray background.
ABOUT THIS MANUALCHAPTER 19iGATE 15.0. Revised: 2009.1.3 SAFETY SYMBOLSThe following symbols are used to indicate important information and to describe levels of possible danger.NoteUseful information with no safety implications.AttentionInformation that must be adhered to as it is necessary to ensure that the system func-tions correctly and to avoid material damage.WarningDanger. Could cause personal injury or damage to the system.Dangerous voltageCould cause injury by high voltage and/or damage the system.Electrostatic dischargeComponents at risk of discharge must be grounded before being touched.ii!!!!
SAFETY AND SECURITY PRECAUTIONSCHAPTER 210iGATE 15.0. Revised: 2009.2 SAFETY AND SECURITY PRECAUTIONSPlease be sure and take time to read this section to ensure your personal safety and proper operation of your TELESInfrastructure System. To avoid personal injury or damage to the system, please follow all safety instructions before you begin workingon your TELES Infrastructure System.TELES Infrastructure Systems are CE certified and fulfill all relevant security requirements. The manufacturer as-sumes no liability for consequential damages or for damages resulting from unauthorized changes. This chapter applies for all Access Gateways. Information that applies only for individual Access Gateways specifiesthe system for which it applies.2.1 SAFETY MEASURES2.2 FCC / INDUSTRY CANADA NOTICE This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equip-ment must be installed and operated with a minimum distance of 58cm between the antennae and all persons.Danger of electric shock - the power supplies run on 230 V. Unplug the TELES Infra-structure System from its power source before working on the power supply or ex-tension socket. Bear in mind that telephone and WAN lines are also energized and can cause electric shocks.Do not insert foreign objects into openings in the device. Conductible objects can cause short circuits that result in fire, electric shock or damage to the device.Do not open the TELES Infrastructure System except to install an additional TELES.Component. Changes in the device are not permitted.Make sure to install the system near the power source and that the power source is easily accessible. Wire your system using only the cables included in the package contents. Use only proper ISDN and Ethernet cables. Be sure to respect country-specific regulations, standards or guidelines for accident prevention.The following information applies for the iGATE GSM only. Changes or modifications not expressly approved by the party responsible for com-pliance could void the user's authority to operate the equipment!!!!
SAFETY AND SECURITY PRECAUTIONSCHAPTER 211iGATE 15.0. Revised: 2009.The magnet bases on the antennae of one iGATE are tested to operate at a minimum distance of 10cm to eachother. A minimum distance of 262cm must be maintained between each antenna-iGATE constellation and all otheriGATEs, antennae, and/or transmitters of any kind.The iGATE has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 ofthe FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a resi-dential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installedand used in accordance with the instructions, may cause harmful interference to radio communications. However,there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harm-ful interference to radio or television reception, which can be determined by turning the equipment off and on, theuser is encouraged to try to correct the interference by one or more of the following measures:Reorient or relocate the receiving antenna.Increase the separation between the equipment and receiver.Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.Consult the dealer or an experienced radio/TV technician for help.2.3 TIPS FOR EMC PROTECTION2.4 SYSTEM SECURITYThis section describes all points crucial to the TELES Infrastructure System’s system security.The system’s location must support normal operation of TELES Infrastructure Systems 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 horizontally in a clean, dry, dust-free lo-cation. If possible, use an air-conditioned site. The site must be free of strong elec-trical or magnetic fields, which cause disrupted signals and, in extreme cases, system failure. Temperature: The site must maintain a temperature between 0 and 45°C. 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.!!!!
SAFETY AND SECURITY PRECAUTIONSCHAPTER 212iGATE 15.0. Revised: 2009.2.5 SERVICING THE SYSTEMRegular servicing ensures that your TELES.System runs trouble-free. Servicing also includes looking after the roomin which the system is set up. Ensure that the air-conditioning and its filter system are regularly checked and thatthe premises are cleaned on a regular basis.2.5.1 REPLACING COMPONENTSIf your system contains any of the following components, replace them according to the following table:2.5.2 PROTECTING THE OPERATING SYSTEMChanging configuration data and/or SIM card positions may lead to malfunctions and/or misrouting, as well as pos-sible consequential damage. Make changes at your own risk. TELES is not liable for any possible damage resultingfrom or in relation to such changes. Please thoroughly check any changes you or a third party have made to yourconfiguration!Make sure your hard disk or flash disk contains enough storage space. Downloading the log files and deleting themfrom the system on a regular basis will ensure your system’s reliability.Power: The site must contain a central emergency switch for the entire power source.The site’s fuses must be calculated to provide adequate system security. The 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.Antenna: iGATE contains no provision or protective device against power surges or lightning strikes.The installation of the antenna must fulfill all necessary safety requirements. Employ the services of a professional antenna installer.Table 2.1 Component Life Span Component Life spanFilter pads 6 monthsPower adapter 5 yearsFan 5 years
SAFETY AND SECURITY PRECAUTIONSCHAPTER 213iGATE 15.0. Revised: 2009.Be careful when deleting files that you do not delete any files necessary for system operation.2.6 CDR FILESCall Detail Records are intended for analysis of the system’s activity only. They are not designed to be used forbilling purposes, as it may occur that the times they record are not exact.2.7 NETWORK SECURITYEvery day hackers develop new ways to break into systems through the Internet. While TELES takes great care toensure the security of its systems, any system with access through the Internet is only as secure as its user makesit. Therefore, to avoid unwanted security breaches and resulting system malfunctions, you must take the followingsteps to secure your TELES.System if you connect it to the Internet:Use an application gateway or a packet firewall.To limit access to the system to secure remote devices, delete the default route and add individual securenetwork segments. Access to the system via Telnet, FTP, GUI, GATE Manager or remote vGATEDesktop must be passwordprotected. Do not use obvious passwords (anything from sesame to your mother-in-laws maiden name).Remember: 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 systemThe firewall must be able to check the following information and only allow trusted users to access the TELES.Sys-tem: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 vGATE Control Unit:Do not use Ctrl/Alt/Del (Task Manager) to shut down vGATEDesktop or vGateCtrl. Do not perform queries on the database. This can result in damages to the database. Do not use any MySQL tools, such as MySQL-Front to make changes in or perform tests on the database.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.!!ii
SAFETY AND SECURITY PRECAUTIONSCHAPTER 214iGATE 15.0. Revised: 2009.For operation and remote administration of your TELES.System, open only the following ports only when the indi-cated services are used: Table 2.2 Default Ports Used for Specific Services Service Protocol PortFor all systems except vGATEFTP TCP 21 (default, can be set)Telnet (for TELES debug access only)TCP 23 (default, can be set)SMTP TCP 25DNS forward UDP 53HTTP TCP 80 (default, can be set)SNTP UDP 123SNMP UDP 161 (default, can be set)H.225 registration, admission, sta-tusUDP 1719 (default, can be set)H.225 signaling TCP 1720 (default, can be set)Radius UDP 1812 (default, can be set)Radius accounting UDP 1813 (default, can be set)GATE Manager TCP 4445 (default, can be set)SIP signaling UDP / TCP 5060 (default, can be set)RTP UDP 29000-29120 (default, can be set)vGATE Control Unit TCP 57343vGATE tunneling TCP 4446For vGATE Control Unit and iMNPFTP TCP 21Telnet TCP 23MySQL database TCP 3306iGATE or VoIPBOX GSM 4 FX to vGATETCP 57342vGATE tunneling to iGATE or VoIPBOX GSM 4 FXTCP 4446
SAFETY AND SECURITY PRECAUTIONSCHAPTER 215iGATE 15.0. Revised: 2009.iGATE or VoIPBOX GSM 4 FX to iMNPTCP 9003Remote vGATEDesktop TCP 57344Remote vGATEDesktop (read only) TCP 57345For vGATE Sim UnitvGATE Control Unit plus iGATE or VoIPBOX GSM 4 FXTCP 51500For NMSFTP TCP 21Telnet TCP 23MySQL database TCP 3306NMS protocol TCP 5000NMS update TCP 5001NMS task TCP 5002NMS task TCP 5003NMS Listen TCP 4444For vGATE Call ManagerRadius authentication UDP 1812Radius accounting UDP 1813Connection from a vGATE Control Unit to a iGATE requires ICMP access. The TCP fil-ters listed above are activated in the default configuration of the vGATE Control Unit or the NMS server.Table 2.2 Default Ports Used for Specific Services (continued)Service Protocol Portii
OVERVIEWCHAPTER 316iGATE 15.0. Revised: 2009.3 OVERVIEWMobile phone charges have become an impor-tant cost factor for many carriers and compa-nies. Connections from the fixed network tomobile networks share a considerable amountof these costs. The iGATE can help reduce these costs up to70%, because calls from mobile network tomobile network cost significantly less thancalls from the fixed network to mobile net-works. Fixed-to-mobile calls that travelthrough the iGATE are routed and billed as ifthey occurred within the same mobile network.You can insert SIM cards from any carrier intothe SIM4 or SIM24 module.Depending on whether your system includes iGATE 4 GSM Boards, iGATE 4 CDMA Boards oriGATE 4 UMTS Boards, each iGATE can provide direct access to the GSM, CDMA or UMTS mobile network with upto 32 mobile channels – 4 mobile channels per iGATE 4 Mobile Board or up to 8 iGATE 4 Mobile Boards per iGATE.The TELES.iGATE Antenna Splitter Board combines the antennas so that only one or two antennas leave the sys-tem. The iGATE has 2 optional PRI ports, optional BRI ports and VoIP functionality, which provides up to 32 VoIP chan-nels, so connection of the mobile gateway occurs by VoIP. The iGATE combines the cost savings resulting fromimplementation of the iGATE with those of Voice over IP transmission. iGATEs can be set up in various national orinternational locations.The iGATE features packages are modular expansion applications that provide services in addition to those offeredwith the standard software. Feature packages can be activated separately or in combination with one another, sothat you can design your system according to your own needs.The iGATE supports all of the following standards:GSM (Global System for Mobile Communications)CDMA (Code-Division Multiple Access)UMTS (Universal Mobile Telecommunications System)Throughout this manual, the following boards will be referred to as iGATE 4 Mobile Board, unless otherwise spec-ified:iGATE 4 GSM BoardiGATE 4 CDMA BoardiGATE 4 UMTS BoardPSTN
OVERVIEWCHAPTER 317iGATE 15.0. Revised: 2009.3.1 WHAT’S NEW IN VERSION 15.0vGATE RoutingManager supportEmails to SMS: support for SMS delivery reportGSM-specific configuration parameters now definable per mobile network (LAIN)Automatic test call to verify poor ASRSupport for vGATE sub-limits used depending on DAD prefixMINA parameter defines minimum number of alert events before Alert message is sentEmail messages can trigger calls and play attached announcementsPrepaid SIMs: Period can signify decimal point or thousands separatorPossible to send OAD instead of DAD to iMNPEmail to SMS conversion: Email can comtain ready encoded SMS-PDUMissed-call SMS also for analog portsImproved µ-law supportCalls to DTMF are not connected; only Call Proc are generatedLicense required for Radiusfailedlog has replaced rruflog
OVERVIEWCHAPTER 318iGATE 15.0. Revised: 2009.3.2 FEATURESEasy installation with QuickstartConversion of PRI (optional) or VoIP to up to 32 mobile channels and vice versaRequires only two antennas for 32 mobile channels with TELES.iGATE Antenna Splitter BoardCentralized SIM management with vGATE Call distribution/rerouting of temporarily unavailable mobile channelsAutomatic use (configurable) of the defined SIM cards per mobile channel Enblock and overlap receivingConversion of call numbersInband tone detectionCan block specified telephone numbers and servicesSummarizes reject causes based on definable cause valuesRemote administration via Ethernet or ISDNOnline monitoring, management and configuration via GATE Manager and NMS (Network ManagementSystem)Generates CDRs and transmits online CDRs (optional)Time-controlled configuration (optional)Built-in cutting edge LCR: Full-featured TELES least cost routing between PBX and PSTN (optional)Optional 24 SIM-card carrier can handle up to 24 SIM cards on 4 mobile channels; SIMs can be randomlydistributed at will (optional)Callback function supported (optional)Direct Line Access function (optional)Number Portability (optional)PPP client/server modeSupports the CAS R2 protocolSupports the NI2 protocolSupports the T1 line typePossible to configure individual mobile bandsSupports PPP dialup via UMTSRadius accounting request contains SIM’s IMSI to enable SIM-specific billingIntegrated mail client capable of SMTP authentication
OVERVIEWCHAPTER 319iGATE 15.0. Revised: 2009.VoIPModular 16 to 180 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Gatekeeper supportRegistrar supportRTP multiplexingSTUN (support for non-static IP addresses)ENUM (changes phone numbers into IP addresses)Configurable time interval for echo detection in VoIP3.3 HOW IGATE WORKSThe iGATE is connected to the PSTN or an IP network and to the mobile network.During outgoing calls from the PSTN or IP network to mobile, dialed digits are compared with the routing-table entries for various mobile networks. The calls are then routed through the corresponding SIMs in theiGATE and forwarded to the number dialed.Only the connection from the SIM in the iGATE to the mobile number in the same mobile network ischarged.3.4 SUPPORTED IMPLEMENTATION SCENARIOSIn each of the following scenarios, calls are routed through individual gateways into the mobile network:a) Integration in a carrier network:One or more mobile gateways areconnected to the carrier network. Thecarrier network routes mobile connec-tions to the individual mobile gate-ways, which then terminate themobile calls. PSTN
OVERVIEWCHAPTER 320iGATE 15.0. Revised: 2009.b) Connection to a centralized SIMserver (vGATE): The mobile gate-ways are integrated in the vGATEthrough the IP network. All SIM cardsin the vGATE network are installed inand maintained from a central server,so that it is no longer necessary to in-stall SIM cards into each iGATE. ThevGATEDesktop makes it possible toassign SIMs virtually to random portsand various times without physicallyremoving the SIMs from thevGATE Sim Unit. c) Last mile connection via mobile:The mobile gateways are set up atspecific locations. The mobile gatewaycan multiplex the available mobilechannels, as well as directly connectISDN subscribers (voice connectionsonly).d) Callback with DTMF: The user callsa number that is defined so that theuser will be called back based on hisOAD. An alerting occurs. The userhangs up and is called back. After theuser has taken the call, the destina-tion number is entered using DTMFtones. When he has finished dialing,the connection to the destinationnumber is established. IPNetworkPSTNCall/SMS Callback2ndLeg2ndLeg
OVERVIEWCHAPTER 321iGATE 15.0. Revised: 2009.e) Callback for international roam-ing: The user with an internationalmobile (prepaid SIM) calls a pre-defined number in the system. Analerting occurs. The user hangs upand is called back based on her OAD.After she accepts the call, she entersthe destination number, which is inthe same country as the system. Thisscenario is for employees who travelabroad, as it eliminates high interna-tional roaming fees.f) Least Cost Routing for termina-tion of mobile calls: The mobilegateway with integrated LCR is set upbetween the existing PBX and thePSTN. The system’s LCR recognizescalls to the mobile network and sendsthem through the mobile gateway tothe mobile network.g) 2nd Generation LCR with VoIP:One or more mobile gateways areconnected to the carrier’s IP backboneor the public Internet by VoIP. The car-rier network routes mobile connec-tions to the individual mobilegateways, which then terminate themobile calls accordingly.Call/SMS CallbackviaPSTN2ndLeg2ndLegPSTN2ndLegInternationalBorderBRI/PRIPSTNBRI/PRIBRI/PRIPSTNBRI/PRIIPNetworkVoIP
OVERVIEWCHAPTER 322iGATE 15.0. Revised: 2009.h) Sending SMS by email: The mobilegateway is connected by Ethernet tothe IT network. It implements anSMTP server (e-mail server). Emailmessages sent to this SMTP server areforwarded to the recipient as SMSmessages through the mobile gate-way.LAN
INSTALLATIONCHAPTER 423iGATE 15.0. Revised: 2009.4 INSTALLATIONFollow the easy instructions to set up your iGATE in a matter of minutes. Implementation of individual scenariosrequires adjustments to the appropriate interfaces. Tips for basic settings are described here. Links to relevantchapters are provided for more specific configuration changes.4.1 CHECKLISTThe following checklist provides step-by-step installation instructions.1. Check the package contents2. Install the device3. Connect the Ethernet4. Connect the E1 trunks (optional)5. Connect the BRI lines (optional)6. Connect the antennas7. Using Quickstart, set the configuration (IP address)8. Check functionality (using the LEDs)9. Secure the LAN connection10. Secure connection with the configuration program4.2 PACKAGE CONTENTSYour iGATE package contains the following components. Check the contents to make sure everything is completeand undamaged. Immediately report any visible transport damages to customer service. If damage exists, do notattempt operation without customer-service approval:1 iGATE1 power supply cable1 or 2 RJ-45 ISDN cables with gray connectors; 5 meters (optional)1 or 2 RJ-45 ISDN cables with green and blue connectors; 5 meters (optional)1 RJ-45 LAN cable with gray connectors; 3 meters1 copy of quick installation instructions1 CD containing Quickstart, GATE Manager, system manual and default configuration filesMobile antennas (optional)4.3 HARDWARE DESCRIPTIONThroughout this manual, the following boards will be referred to as iGATE 4 Mobile Board, unless otherwise spec-ified:iGATE 4 GSM BoardiGATE 4 CDMA BoardiGATE 4 UMTS Board
INSTALLATIONCHAPTER 424iGATE 15.0. Revised: 2009.The iGATE is available in expansion levels from 4 to 32 mobile channels. The following pages describe installationof the iGATE.Figure 4.1 > shows the rear view of a iGATE, which contains the following boards:Left side from top to bottom:iGATE 4 Mobile Board (for mobile channels 1-4)iLCR Base BoardOptional TELES.iGATE Antenna Splitter BoardRight side from top to bottom:Optional iGATE 4 Mobile Board (for mobile channels 13-16)Optional iGATE 4 Mobile Board (for mobile channels 9-12)Optional iGATE 4 Mobile Board (for mobile channels 5-8) Figure 4.1 2 HU iGATE: Rear ViewFigure 4.2 > shows the rear view of a iGATE BRI, which contains the following boards:Left side from top to bottom:iLCR 4BRI BoardiLCR Base BoardOne empty slotRight side from top to bottom:One empty slotiGATE 4 Mobile Board (for mobile channels 5-8)Optional iGATE 4 Mobile Board (for mobile channels 1-4)Figure 4.2 2 HU iGATE BRIPower PRI 2PRI 1Ethernet10/100 Base-TAntennaSIM-CardCarrierAntennaPowerPRI 2(opt.)PRI 1(opt.)Ethernet10/100 Base-TAntennaSIM-CardCarrier (opt.)4 BRI Ports
INSTALLATIONCHAPTER 425iGATE 15.0. Revised: 2009.Figure 4.3 > shows the rear view of a iGATE, which contains the following boards:From left to right:iLCR Base BoardiGATE 4 Mobile Board (for mobile channels 1-4)iGATE 4 Mobile Board (for mobile channels 5-8)iGATE 4 Mobile Board (for mobile channels 9-12)iGATE 4 Mobile Board (for mobile channels 13-16)Optional TELES.iGATE Antenna Splitter BoardiGATE 4 Mobile Board (for mobile channels 17-20)Optional iGATE 4 Mobile Board (for mobile channels 21-24)Optional iGATE 4 Mobile Board (for mobile channels 25-28)Optional iGATE 4 Mobile Board (for mobile channels 29-32)Figure 4.3 4HU iGATE4.4 INSTALLATION REQUIREMENTSBefore installing your iGATE, make sure you have the following connections in place:Ethernet connectionAntenna connection(s)Optional ISDN PRI connection to PSTN and/or to the PBXPowerIf the system is not connected to a vGATE, insert the SIM cards into the SIM-card carrier, the SIM-cardcarrier into the iGATE 4 Mobile Board.4.4.1 ETHERNET WIRINGTo connect the iGATE’s Ethernet port to your local network, connect the system to an Ethernet switch or hub inyour network. Use the three meter cable with gray connectors.Power AntennaSIM-CardCarrierEthernet10/100 Base-TPRI 2PRI 1 Antenna
INSTALLATIONCHAPTER 426iGATE 15.0. Revised: 2009.If you want to connect the iGATE directly to your computer and a connection cannot be established, use a cablewith the following pin assignment: 4.4.2 PRI WIRING4.4.2.1 TELES TO TBR12If you are connecting a iGATE to E1 and need to change the assignment of an adapter, assign the pins as follows.Connectors on cables included with the iGATE will be gray for TELES TE and gray for NT on the remote device, bluefor TELES NT, and green for TE on the remote device:4.4.2.2 FORMER TELES ASSIGNMENT TO CURRENT TELES ASSIGNMENTIf you are connecting a system with the former TELES assignment to one with the current TELES assignment, con-nectors will be yellow for former TE or NT and green for current TE or NT. Pin assignment will be as follows: 1278345678345612RX+RX-TX+TX- TX-TX+RX+RX-Connector 1 Connector 2Abbreviations: TX - Transmit / RX - Receive783456RXRXNetworkInterface127834RX5RX6TXTe r m i na lInterface12TXTXTXTELES System/TE TBR12/NTAbbreviations: TX - Transmit / RX - ReceiveGray Gray127834RX5RX6TXTX783456RXNetworkInterface12TXTXRXTe r m i na lInterfaceTELES System/NT TBR12/TEAbbreviations: TX - Transmit / RX - ReceiveGreenBlue12783456RXRXTXTX78345612TXTXRXRXTELES SystemFormer TELESEquipmentAbbreviations: TX - Transmit / RX - ReceiveGreen Yellow
INSTALLATIONCHAPTER 427iGATE 15.0. Revised: 2009.4.4.3 BRI WIRINGIf your system contains optional iLCR 4BRI Board, the connection to the PBX or PSTN lines occurs with the RJ45connectors. Each connector's pin out is for BRI line:Pins 1, 2, 7, and 8 are not used. TE refers to terminal endpoint (connection to PSTN). NT refers to network termi-nation Layer 1 (connection to PBX).4.4.4 ANTENNA CONNECTIONPlug an antenna cable into each of the SMA jacks. If the system contains a TELES.iGATE Antenna Splitter Board,plug the antenna(s) in there. If not, plug them into the jacks on the iGATE 4 Mobile Board.4.4.5 SIM CARDSEach iGATE 4 Mobile Board has a slot for a SIM-card carrier. Insert the SIMs in the SIM-card carrier and then insertthe SIM-card carrier into the iGATE 4 Mobile Board.If the system is connected to a vGATE, the SIM cards will be inserted into the vGATE Sim Unit and not into theiGATE.Table 4.1 BRI WiringRJ-45 TE NT Polarity3 Transmit Receive +4 Receive Transmit +5 Receive Transmit -6 Transmit Receive -Antennas connected to the iGATE must be installed by a qulaified technician accord-ing to all necessary safety requirements and the antenna’s installation specifications. The antenna adaptor does not provide power surge protection.You must configure the PINs in the pabx.cfg before inserting the SIM-card carrier unless the SIM has no PIN or the PIN is 0000.iiii
INSTALLATIONCHAPTER 428iGATE 15.0. Revised: 2009.4.4.5.1 THE SIM-CARD CARRIER MODULEThe SIM-card carrier module contains the SIM cards for the individual mobile channels. Each iGATE 4 Mobile Board(standard) contains one module, which can be inserted into and removed from the back of theiGATE 4 Mobile Board during operation. Depending on the modules specifications and version, up to six SIM cardscan be implemented in each mobile channel or you can assign SIMs to individual mobile channels as you wish (seeTable 5.16 >). SIM cards are mounted on the front and back of the SIM24 module (optional) or the front of the SIM4 module(Figure 4.4 >). As a guide to help you distinguish top from bottom on the SIM24 module, SIM0-5 and SIM12-17 are printed in the upper corner near the module’s blue handle, as shown in Figure 4.4 >. The SIMs on theSIM4 module are numbered from right to left, with one SIM assigned to each mobile channel in ascending order.You can select the SIM cards you would like to use via software. Individual SIM cards on each channel can be activein different Timezones, or they can be reassigned following a time limit or call.Figure 4.4 SIM-Card Carrier Modules678 910 11012 34 512 13 14 15 16 1718 19 20 21 22 23SIM0-5SIM6-11SIM12-17SIM18-2303 2 1 SIM24 ModuleFront ViewSIM24 ModuleRear ViewSIM4 Module
INSTALLATIONCHAPTER 429iGATE 15.0. Revised: 2009.If a SIM24 carrier is used, entries in the subscriber line of the configuration file pabx.cfg or in nightfiles refer tothe SIM positions for each mobile controller. The SIM positions and mobile controllers correspond with the physicalSIM slots on the SIM-card carrier module as shown in Table 4.2 >: Insert ONLY the SIM-card carrier module into the iGATE 4 Mobile Board!Table 4.2 SIM-Card PositionsSlot Physical Mobile Port per BoardSIM-Card Position01112123134141252263274281392310 3 311 4 312 1 413 2 414 3 415 4 416 1 517 2 518 3 519 4 5!!
INSTALLATIONCHAPTER 430iGATE 15.0. Revised: 2009.Example: In the following example, SIMs from various SIM positions in the SIM24 carrier are assigned toindividual GSM controllers. Bear in mind that the first GSM controller on the iGATE 4 GSM Boardhas the physical controller number 00 in the system. SIM 1, which corresponds with slot 0 on theSIM24 carrier, is assigned to the first GSM controller. 20 1 621 2 622 3 623 4 6Physical Controller Number in the SystemMobile Controller on the iGATE 4 Mobile BoardSIM Card Position for the Mobile ControllerSlot in the SIM24 Car-rier08 1 1 009 2 3 910 3 2 611 4 6 23Subscriber08 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24] CHADDR ALARM NEXTSubscriber09 = TRANSPARENT ROUTER GSM[0000,00000,+00000,3,1,1,SIM24] CHADDR ALARM Subscriber10 = TRANSPARENT ROUTER GSM[0000,00000,+00000,2,1,1,SIM24] CHADDR ALARMSubscriber11 = TRANSPARENT ROUTER GSM[0000,00000,+00000,6,1,1,SIM24] CHADDR ALARMTable 4.2 SIM-Card PositionsSlot Physical Mobile Port per BoardSIM-Card Position
INSTALLATIONCHAPTER 431iGATE 15.0. Revised: 2009.4.5 PREPARING FOR INSTALLATIONEach computer that is to communicate with the iGATE requires a network connection. Please have the followinginformation for connection to your network available:IP address in the local network for the iGATE to be configuredNetmask for the iGATE to be configuredDefault gateway for iGATE to be configuredDNS server addressNTP server address4.6 HARDWARE CONNECTIONConnect your computer with the local networkConnect the iGATE with the local networkIf you choose to connect the iGATE to ISDN, use the ISDN connection cables included in the packagecontents to connect the iGATE with your PBX and/or the PSTN according to the required portconfiguration.Connect the iGATE to the power supply.4.7 STARTUP WITH QUICKSTARTQuickstart is an application that helps you to configure the IP settings of your iGATE quickly and conveniently with-out changing any network settings on your computer. Quickstart can be installed on any of the following operating systems:Windows 2000Windows XPWindows VistaIf you are using any of these operating systems, please follow the instructions in this chapter. If you are using anon-Windows operating system (e.g. Linux) follow the instructions in Chapter 4.9 >.Bear in mind that the preconfigured iGATE’s default IP address is 192.168.1.2. If it is already being used in your local network, you must run Quickstart without a connec-tion to your local network. This can occur using a back-to-back Ethernet connection from your computer to the iGATE. If the desired IP address for the iGATE is not in your network, you must assign your computer a temporary IP address from this range.ii
INSTALLATIONCHAPTER 432iGATE 15.0. Revised: 2009.4.7.1 INSTALLING QUICKSTARTMake sure the GATE Manager is not run-ning on your computer. To install Quick-start on your computer, insert the CD andselect Quickstart from the menu. When asked if you want to install compo-nents on your machine, click Install.Click Next in the introduction window tobegin installation of the Quickstart. Once installation begins, click Next to in-stall Quickstart in the predefined folder.To install it in another location, clickBrowse and select a folder from thebrowser that appears. Then click Next.Click Close to exit when installation iscomplete.
INSTALLATIONCHAPTER 433iGATE 15.0. Revised: 2009.4.7.2 CONFIGURATION WITH QUICKSTARTFigure 4.5 QuickstartNow you can use Quickstart, to set up your iGATE’s IP configuration. Open Quickstart.exe. The program will au-tomatically search for your iGATE in the local network. For Quickstart, the source UDP port is 57445. It might benecessary to change the firewall rules on your system. Click the Search button if you would like to restart the search. When the program has found your iGATE, it willappear in the window. As soon as it appears, you can end the search by clicking Stop.The system’s icon will appear in gray if it is unconfigured. Once it has been configured, it will appear in green. Theserial number appears as the system’s name. The iGATE is partially preconfigured. The configuration filespabx.cfg and route.cfg are already on the system. Only the system’s IP-related entries must be set. Individ-ual port adjustments are to be made manually later. Port properties can be changed and parameters can be as-signed then.To change the appearance of the window, select Large Icons, Small Icons or Details from the View menu. Inthe following description, we will use the Details View, which contains the following columns:Table 4.3 Quickstart Details View ColumnsHeading DefinitionIdentifier This column lists the iGATE’s serial number.IP Address This column lists the iGATE’s IP address.Configured An X means the iGATE contains the configuration files.# of VoIP Ctrls This column lists the number of VoIP Modules installed in the iGATE. Each VoIP Module represents one VoIP controller.VoIP Channels This column shows the number of VoIP channels per VoIP Module.Type Lists the type of the system.Box An X means the system is a VoIPBOX BRI.CF Mounted An X means the iGATE contains a compact flash disk.
INSTALLATIONCHAPTER 434iGATE 15.0. Revised: 2009.In the Options menu, you can suppress or activate ICMP ping to test the Internet connection.To perform the initial configuration of the system, double-click the icon or right-click and select Configure. The IPSettings dialog will appear. If you are using a DHCP serv-er, activate the checkbox DHCP. This will deactivate thenext four lines. Your DHCP server will automatically provideall of the other necessary information. If you do not have aDHCP server, leave the DHCP checkbox empty. The defaultIP address appears in the IP Address box. Enter a new IPaddress. If the address you enter already exists in the net-work, you will be notified to choose another address at theend of the configuration process. Enter the system’s net-mask in the Mask dialog box. Enter the IP address for theDefault Gateway and the Time Server in the corre-sponding dialog boxes. Select the Time Zone for the loca-tion of the system. Click Finish. Now the IP settings are configured; all other processes run automatically. First the system’s IP address will bechanged and then the system will start with the new IP address. If you right-click the system’s icon in the main window and choose Temporarily Configure IP Address, only theIP address for the system’s first Ethernet interface and the netmask will be temporary changed. This can be helpfulif you want to set up local remote access to the system and use other IP settings on the remote device than thesystem’s IP configuration in the network. Bear in mind that the functions on the system’s first Ethernet interfacework with the new settings.Now you can complete the system’s configuration using the GUI (cf. Chapter 4.8 on page 35 >).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.6 Quickstart Configuration: IP Settingsii
INSTALLATIONCHAPTER 435iGATE 15.0. Revised: 2009.4.8 STARTUP VIA GUIFigure 4.7 GUISystem configuration can occur via the GUI. We recommend you use Internet Explorer 6/7. Simply open a browser,enter the system’s IP address in the address bar, and click Login in the navigation menu on the left. Enter theusername teles-carrier and the password tcs-carrier to access the system. Figure 4.8 GUI FaststartUsing the navigation menu on the left, click Faststart to configure the system. Follow the steps as they appear.
INSTALLATIONCHAPTER 436iGATE 15.0. Revised: 2009.4.9 STARTUP VIA FTPIf you are using a computer that does not use a Windows operating system, you can preconfigure the iGATE viaFTP. The iGATE’s default IP address is 192.168.1.2. To configure the iGATE using FTP, you must assign your com-puter an IP address from network range 192.168.1.0 Class C and then access the iGATE via FTP.The default user is teles and the default password is tcs-ag. To configure the system, use the default configurationfile example on the CD in the Configfiles directory and the following four subdirectories:IPconfigThis subdirectory contains the file (ip.cfg) responsible for configuration of the Ethernet interface.carrierThis subdirectory contains a configuration (pabx.cfg, route.cfg) for iGATE 32 withiGATE 4 GSM Boards and VoIP.corporateThis subdirectory contains a configuration (pabx.cfg, route.cfg) for iGATE 16 withiGATE 4 GSM Boards.umts_systemThis subdirectory contains a configuration (pabx.cfg, route.cfg) for iGATE 16 withiGATE 4 UMTS Boards.bri_systemThis subdirectory contains a configuration (pabx.cfg, route.cfg) for iGATE 8 withiGATE 4 GSM Boards and an optional iLCR 4BRI Board.To edit the default configuration, follow the directions in Chapter 5 >. Upload the configuration files into the /boot directory.4.10 SELF PROVISIONING WITH NMSWith a management connection to the NMS (Network Management System), the iGATE can retrieve its configura-tion files from the configured NMS. That means that custom configuration of the device occurs automatically whenthe 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 device’s TAG number tosend a prepared configuration. For further information on configuration of the NMS, please refer to the NMS Sys-tems Manual.4.11 LED FUNCTIONALITY4.11.1 ILCR BASE BOARD PRI PORT LEDSEach PRI port has one red and one green LED to show the port’s status.
INSTALLATIONCHAPTER 437iGATE 15.0. Revised: 2009.The red LED displays the status of the bypass relay that connects the ports with each other when the PRI port’srelays are off. That means when the system is connected between a PBX and the PSTN, it is transparent when theLED is red.The green LED displays whether or not layer 1 is active on the PRI port’s connected cable. 4.11.2 IGATE 4 MOBILE BOARD SIM-CARD LEDSOn the spine of the iGATE 4 Mobile Board, to the right of the SIM card module,two columns of green LEDs display the status of each mobile channel. The LEDs in the upper column show the general operational status of the SIMcards, while the status of the mobile channels is displayed in the lower column.Table 4.5 > contains a description of the LEDs and what they mean:Table 4.4 iLCR Base Board PRI Port LEDsLED DescriptionRed on The system and bypass relay are inactive (normally during the startup phase).Red off The system has started and the bypass relay is active.Green on Layer 1 is active.Green off Layer 1 is inactive.SIMGSMGSM Channel 1GSM Channel 2GSM Channel 3GSM Channel 4GSM Channel 1GSM Channel 2GSM Channel 3GSM Channel 4OperationLEDsConnectionLEDsAnt
INSTALLATIONCHAPTER 438iGATE 15.0. Revised: 2009.Table 4.5 iGATE 4 Mobile Board LEDs 4.12 REMOTE ACCESS AND ACCESS SECURITYAfter the system has been configured and all cables are connected, remote administration and maintenance canoccur with the GATE Manager (Chapter 4.12.1 >), the GUI (Chapter 4.12.2 >)or via FTP (Chapter 4.12.3 >).Operational Sta-tusConnection Status DefinitionOff Off The mobile channel is not operational because:No external power supplySIM module slot is emptyNo SIM cardOff Blinking slowly Not possibleOff Blinking quickly Not possibleOff On Not possibleBlinking slowly Off The SIM card is attached, but the mobile channel is not opera-tional because:Mobile channel is in logon phaseMobile channel’s status is unknownBlinking slowly Blinking slowly Not possibleBlinking slowly On Not possibleBlinking quickly Off The mobile channel is not operational because:SIM card has been blockedReception field strength below limitBlinking quickly Blinking slowly Not possibleBlinking quickly Blinking quickly Status during initializing phase (e.g. system start up). Display changes when status of mobile changes.Blinking quickly On Not possibleOn Off The mobile channel is operational, the SIM card has logged on.On Blinking slowly Not possibleOn Blinking quickly The mobile channel is operational, the SIM card has logged on, a connection is being set up on this channelOn On The mobile channel is operational, the SIM card has logged on, a connection has been set up on this channel
INSTALLATIONCHAPTER 439iGATE 15.0. Revised: 2009.4.12.1 GATE MANAGER Figure 4.9 GATE ManagerThe GATE Manager administration and maintenance software offers a broad range of functions. TheGATE Manager is user friendly and can be customized to suit your needs. The following maintenance functions are possible:Display system information and network element status.Retrieve and display configuration files.Restart network elements.Use of a trace option for checking functions and fault diagnosis. Option to use an external tool, e.g. todisplay and break down trace data.Update the system software (firmware) and configuration tables.Retrieve CDRs (Call Detail Records).Display the current connections (status).Display statistical information for network elements and interfaces.Display the status of the interfaces.Use the CD enclosed in your package contents to install the GATE Manager. 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 originationTCP port and port 4445 as destination port. The following default value (4445) is configured in the pabx.cfgfile for the system’s port: In the default configuration, ISDN access is disabled. To configure the system so that certain data calls are receivedas remote administration calls, make the following changes in the pabx.cfg: RemoteCode=BBBMapAll<num>=BBB DATAMake the following entries in the route.cfg if the system is to handle all data calls as remote-administration calls:MoipPort=4445
INSTALLATIONCHAPTER 440iGATE 15.0. Revised: 2009. 4.12.2 GRAPHICAL USER INTERFACERemote access can occur via the GUI. Even users with little experience can easily configure standard system settingswith this interface. Simply open a browser and enter the system’s IP address in the address bar. The following administrative levels apply:Carrier Mode (Full Access)User: teles-carrierPassword: tcs-carrierAll configuration pages can be accessed in this mode.Administrator ModeUser: teles-adminPassword: tcs-adminThis access level is for the user network’s administrator. All IP and routing entries, with the exception of VoIP carrierentries, can be set here.MapAll0=BBB DATAMapAll1=BBB DATAMapAll2=BBB DATAMapAll3=BBB DATAMapAll4=BBB DATAMapAll5=BBB DATAMapAll6=BBB DATAMapAll7=BBB DATAMapAll8=BBB DATAMapAll9=BBB DATA
INSTALLATIONCHAPTER 441iGATE 15.0. Revised: 2009.Read-Only ModeUser: teles-userPassword: tcs-userNo 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 inthe ip.cfg in encrypted form:PwdCarrier=<crypt>PwdAdmin=<crypt>PwdUser=<crypt>Example: The user interface is divided into the following main sections: All of the user interface’s pages contain Help buttons and links to the online help, which provides a detailed de-scription of all of the individual configuration settings.[httpd]PwdUser=k24X0sdc.uMcMPwdAdmin=k2UMj19qtovzIPwdCarrier=k2jryo6Xd5vN6Never copy these entries from one system to another, as the encryption is unique for each system.Table 4.6 GUI: Sections Section DescriptionUser Data Here you can change the user passwords and the language for the GUI.System Settings IP Settings: Settings for the Ethernet interfaces and related services.Port Settings: Settings for the VoIPBOX GSM/CDMA 4 FXs ports.VoIP Settings: VoIP settings for the SIP or H.323 carrier.Telephony Routing:Routings for telephone numbers.System Overview Overview of system information and drivers.Telephony Routing VoIP settings for the SIP or H.323 carrier and routings for telephone num-bers.Commands Here you can activate a configuration or restart the system.ii
INSTALLATIONCHAPTER 442iGATE 15.0. Revised: 2009.4.12.3 FTPRemote 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, change to the directory /data if the system con-tains a flash disk. Otherwise change to the directory /boot.The following commands can be carried out via FTP access: 4.12.4 SETTING A PASSWORD FOR REMOTE ACCESSThe 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. Table 4.7 FTP Security Entries FTP SecurityFtpdPort=<port>Defines the FTP access port (default 21).RemotePassword=<password>Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.12.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.8 FTP Commands Command FunctionSITE 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.
INSTALLATIONCHAPTER 443iGATE 15.0. Revised: 2009.Start the program in a command window with the entry mkpwd <password>. The output shows the encryptedpassword. Enter the encrypted password in the configuration file pabx.cfg’s parameter line as follows: When the file has been transferred to the system and the configuration has been activated, access to the systemcan occur only with the password. Don’t forget to memorize the password!If you do not define a password, access to the system via GATE Manager occurs without a password, and FTP ac-cess occurs with the default password tcs-ag.RemotePassword=<crypt>
CONFIGURATION FILESCHAPTER 544iGATE 15.0. Revised: 2009.5 CONFIGURATION FILESThis chapter describes the basic setup and the most commonly used entries for the configuration files. Configura-tion of iGATEs is managed in the following three files: The system comes without the file ip.cfg. The default configuration with the IP address 192.168.1.2 is active whenthis file is 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 GUI to make configuration changes, the files will be adjusted automatically.Make sure you secure the system with new passwords following configuration and remember to memorize thepasswords! These configuration files contain all system-specific settings and are used when the system starts. Comments in-cluded in these files must begin with a semicolon. They do not need to be at the beginning of a line. Configurationfiles must end with an empty line.Please save a backup of the files pabx.cfg and route.cfg before starting configuration.Table 5.1 Configuration FilesFile Functionip.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 and/or SIM card positions 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 with such changes. Please do therefore thoroughly check any changes you or a third party have made to your configuration.ii
CONFIGURATION FILESCHAPTER 545iGATE 15.0. Revised: 2009.The configuration files follow these conventions: Individual files are divided into sections. These sections alwaysbegin with a line entry in square brackets. The basic required sections are in these files: 5.1 CONFIGURATION FILE IP.CFGThe basic settings for the two Ethernet interfaces are entered here. One interface usually suffices. The second in-terface can be used for special requirements, e.g. as a hub port, DSL router or vLAN interface. Generally, thesesettings are entered once and then left unchanged. This file contains the following sections, which must appear in the order given: Table 5.2 Required Configuration File SectionsSection File Function[System] pabx.cfgroute.cfgip.cfgThis section contains the system’s basic settings. [Night<num>]EXAMPLE: [Night1][Night2]pabx.cfgroute.cfgThis 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.3 Sections in the ip.cfg FileSection 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 system’s firewall.
CONFIGURATION FILESCHAPTER 546iGATE 15.0. Revised: 2009.5.1.1 SYSTEM SECTION CONFIGURATIONThe [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 ETHERNET INTERFACE CONFIGURATIONThe system includes two Ethernet interfaces (emac0 and emac1). Only the first is active in the default configuration.Therefore, make sure you plug the cable into the right controller. The second Ethernet interface can be configuredas needed.The following settings are possible for the sections [emac0] (matched to the first Ethernet controller) and [emac1](matched to the second Ethernet controller):IpAddress=<ip addr>/<netmask> The IP address is entered in decimal notation, followed by a slash (/) and the netmask in bit notation.[altqd] (optional) This section enables prioritization of VoIP packets in the iGATE 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.[xppp<x>] (optional) This section contains settings for point-to-point dial-up setup via ISDN.[vlan<x>] (optional) These section(s) contain settings for the virtual networks. <x> can be any-thing from 0 to 9.[System]DefaultGw=192.168.1.254[System]DefaultGw=192.168.1.254Route=10.0.0.0 -netmask 255.0.0.0 192.168.1.1Table 5.3 Sections in the ip.cfg FileSection Function
CONFIGURATION FILESCHAPTER 547iGATE 15.0. Revised: 2009.Example:The following entry is used to allocate an IP address via DHCP: IpAddress=dhcpThe following entry is used in the [emac1] section if operation of the system is occurs in bridge mode.IpAddress=up5.1.3 BRIDGE CONFIGURATIONA 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> upActivating another Ethernet interface in this way is useful, for example, when the Ethernet switch does not haveany more ports available for connection of the system. You can simply unplug a cable and plug it into the system’ssecond Ethernet interface.Example:5.1.4 NAT CONFIGURATIONThe NAT (Network Address Translation) module translates IP addresses from the local network to an IP address orrange on a public interface. All rules are defined in the [nat] section: IpAddress=192.168.1.2/24[bridge0]BrConfig=add emac0 add emac1 upTable 5.4 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 system’s second Ethernet interfacepppoe0 Protocol used for DSL connectionsxppp<0> Protocol used for ISDN and CDMA dial-up connections<local network ad-dress/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.
CONFIGURATION FILESCHAPTER 548iGATE 15.0. Revised: 2009.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 redirected to ports 80and 443 in the local IP address 192.168.1.100.<public network ad-dress/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 entries> Special rules can be defined for some services or protocols. The system can serve as a proxy for FTP: proxy port ftp ftp/tcpSpecial 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 s packets from one port and IP address to another.<interface> Defines the translated interface or protocol:emac1 The system’s second Ethernet interfacepppoe0 Protocol used for DSL connectionsProtocol used for ISDN and CDMA dial-up connections<public network ad-dress/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 ad-dress/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.Table 5.4 NAT Configuration (continued)
CONFIGURATION FILESCHAPTER 549iGATE 15.0. Revised: 2009.5.1.5 PPPOE CONFIGURATIONThe protocol Point-to-Point over Ethernet is used for DSL communication with the DSLAM. That means the systemcan 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 meansusername, password and authentication protocol are set here. The Ethernet interface is emac1 and the gatewaycan also be defined. The parameter PppoeIf defines the physical Ethernet interface used (always emac1). Thesettings are entered as follows:Bear in mind that configuration of the firewall, the NAT module and prioritizationof the VoIP packets must be considered 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 FIREWALL SETTINGSThe firewall settings provide options for limiting or denying access to and from the system. If you do not configurethis section, the firewall is inactive and access is unlimited.Example: In the following example, only port 4445 allows incoming connections from the IP address192.168.1.10. All others will be blocked.[nat]map=emac1 192.168.1.0/24 -> 0/32 proxy port ftp ftp/tcpmap=emac1 192.168.1.0/24 -> 0/32 portmap tcp/udp 40000:60000map=emac1 192.168.1.0/24 -> 0/32rdr=emac1 0/0 port 80 -> 192.168.1.100 port 80 tcprdr=emac1 0/0 port 443 -> 192.168.1.100 port 443 tcp[pppoe0]PppoeIf=emac1 User=userPwd=pwdAuthProto=papRoute=0.0.0.0Make 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.[firewall]fw=pass in quick on emac0 proto tcp from 192.168.1.10/32 to any porteq 4445 flags S keepstate keep frags fw=block in log quick on emac0 all!!
CONFIGURATION FILESCHAPTER 550iGATE 15.0. Revised: 2009.Table 5.5 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 accessblock denies access<direction> Possible directions are in and out:in external to internalout 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.quickAllows 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 out-going 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 4445proto <protocol>defines the protocol, for which the rule is valid (e.g.: proto tcp, proto udp, proto icmp).
CONFIGURATION FILESCHAPTER 551iGATE 15.0. Revised: 2009.Example:5.1.7 BANDWIDTH CONTROLIn many implementation scenarios, the iGATE in router mode (e.g. as DSL router) sends voice and data trafficthrough a connection with limited bandwidth. This can lead to lost voice packets that arrive too late to be used inthe voice stream. To avoid lost packets, this QOS setting prioritizes packet transmission. You must set the priorityfor voice signaling and for the voice packets. That means you must prioritize SIP/H.323, RTP and RTCP. You willfind the ports used in Table 5.13 >, in the following entries:H225PortSipPortVoipRtp Portport eq <num><num> defines the port as number (e.g.: port eq 4445).keep stateEnsures 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 SOnly 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 fragsFragmented packets are also routed.[firewall]; loopbackfw=pass in quick on emac0 allfw=pass out quick on emac0 all; traffic to outgoingfw=pass out quick on pppoe0 proto tcp all flags S keep state keep fragsfw=pass out quick on pppoe0 proto udp all keep state keep fragsfw=pass out quick on pppoe0 proto icmp all keep state keep frags; incoming trafficfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 21 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 23 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state ; icmp trafficfw=pass in quick on pppoe0 proto icmp all keep state; other will be blockedfw=block in log quick on pppoe0 allfw=block out log quick on pppoe0 allTable 5.5 Settings in the [firewall] Section of the ip.cfg (continued)[firewall]fw=<mode> <direction> <list>
CONFIGURATION FILESCHAPTER 552iGATE 15.0. Revised: 2009.VoipRtpPortSpacingDifferent 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. Theparameter VoipRtpPortSpacing shows the next RTP port (RTP port + port spacing).Example: In the following example, prioritization is set for a thirty-channel VoIP connection. The SIP signal-ing port 5060 and the RTP/RTCP ports 29000 to 29059 are prioritized at level 7. All other servicesTable 5.6 Settings in the [altqd] Section of the ip.cfg interface <interface> bandwidth <bw> priqDefines the interface for which the rule applies.<interface> Sets the interface for which prioritization applies (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 for the class.<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 TCP17 for UDP
CONFIGURATION FILESCHAPTER 553iGATE 15.0. Revised: 2009.are set at level 0:5.1.8 DHCP SERVER SETTINGSThe DHCP (Dynamic Host Configuration Protocol) server provides a mechanism for allocation of IP addresses toclient hosts. The section [dhcpd] contains a list of parameters and settings for the DHCP server in the system. Itis divided into global settings for the server and parameters for the DHCP subnet.[altqd]interface pppoe0 bandwidth 512K priqclass priq pppoe0 realtime_class root priority 7 filter pppoe0 realtime_class 0 5060 0 0 0 filter pppoe0 realtime_class 0 0 0 5060 0 filter pppoe0 realtime_class 0 29000 0 0 17 filter pppoe0 realtime_class 0 0 0 29000 17 filter pppoe0 realtime_class 0 29001 0 0 17 filter pppoe0 realtime_class 0 0 0 29001 17 .... filter pppoe0 realtime_class 0 29058 0 0 17 filter pppoe0 realtime_class 0 0 0 29058 17 filter pppoe0 realtime_class 0 29059 0 0 17 filter pppoe0 realtime_class 0 0 0 29059 17 class priq pppoe0 regular_class root priority 0 defaultTable 5.7 Settings in the [dhcpd] Section of the ip.cfg ; Global dhcp parametersallow 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 Subnetsubnet <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 oprion 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.
CONFIGURATION FILESCHAPTER 554iGATE 15.0. Revised: 2009.Example:5.1.9 PPP CONFIGURATION FOR ISDN AND CDMA DIAL-UPThe point-to-point protocol is used for dial-up connection via ISDN lines or via a mobile CDMA connection. Thatmeans the system can set up an Internet connection, which can be used for all local users or to transmit VoIP callsvia ISDN dial-up. Make sure you 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]; Global dhcp parametersallow unknown-clients;ddns-update-style none;; Parameter for the Subnetsubnet 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.7 Settings in the [dhcpd] Section of the ip.cfg (continued); Global dhcp parameters
CONFIGURATION FILESCHAPTER 555iGATE 15.0. Revised: 2009.The advantages of VoIP over ISDN can be seen especially in corporate implementation. For example, it is usefulwhen 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 occursimultaniously 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:Table 5.8 Settings in the [xppp] Section of the ip.cfg [xppp<num>]Dad=<num>Enter the dial-up number. Only digits can be defined here. Any required special characters (* or #) can be set in the mapping entry.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 or pap for the protocol used for authentication.AutoUp=<int>Defines if the PPP interface is activated automatically after system start. The following values are possible:0 = No automatic PPP activation (default)1 = Automatic PPP activationIdleTO=<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 and 120 for CDMA dial-up.Rfc1662=<val>Framing to be used:0 for ISDN or 1 for CDMALcpTO=<msec>Allows you to change the value of the LCP timeout. The timeout-value must be specified in milliseconds (de-fault 1000).
CONFIGURATION FILESCHAPTER 556iGATE 15.0. Revised: 2009.Example:5.1.10 VLAN CONFIGURATIONA VLAN (Virtual Local Area Network) is a virtual LAN within a physical network. Each VLAN is assigned a uniquenumber (VLAN ID) and defined in the [vlan<x>] section with Tag: value between 1 and 4095Priority: 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 beassigned to the vlan1 interface: 5.1.11 EXAMPLES5.1.11.1 DEFAULT CONFIGURATIONIn the following example, the system’s IP address is 192.168.1.1, the netmask is 255.255.255.0, and the standardgateway is 192.168.1.254: StartDelay=<sec>Time in seconds the system will wait to start the ppp process.[xppp0]Dad=12345User=userPwd=pwdRoute=0.0.0.0AuthProto=chapIdleTO=60MTU=1500Rfc1662=0LcpTO=500StartDelay=10[vlan1]IfConfig=vlan 10,7 vlanif emac0IpAddress=192.168.199.1[System]DefaultGw=192.168.1.254[emac0]IpAddress=192.168.1.1/24Table 5.8 Settings in the [xppp] Section of the ip.cfg (continued)[xppp<num>]
CONFIGURATION FILESCHAPTER 557iGATE 15.0. Revised: 2009.5.1.11.2 ACTIVE ETHERNET BRIDGEIn the following example a two-port Ethernet bridge is configured. The system’s 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: [System]DefaultGw=192.168.1.254[emac0]IpAddress=192.168.1.1/24[emac1]IpAddress=up[bridge0]BrConfig=add emac0 add emac1 up
CONFIGURATION FILESCHAPTER 558iGATE 15.0. Revised: 2009.5.1.11.3 INTEGRATED DSL-ROUTER SCENARIO FOR VOIP TRAFFIC WITH AN ACTIVE DHCP SERVER AND FIREWALLIn 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-addressallocation:[System][emac0]IpAddress=192.168.0.2/24[emac1]IpAddress=up[pppoe0]PppoeIf=emac1 User=usertelekomPwd=pwdAuthProto=chapRoute=default[nat]map=pppoe0 192.168.0.0/24 -> 0/32 proxy port ftp ftp/tcpmap=pppoe0 192.168.0.0/24 -> 0/32 portmap tcp/udp 40000:60000map=pppoe0 192.168.0.0/24 -> 0/32[firewall]; loopbackfw=pass in quick on emac0 allfw=pass out quick on emac0 all; traffic to outgoingfw=pass out quick on pppoe0 proto tcp all flags S keep state keep fragsfw=pass out quick on pppoe0 proto udp all keep state keep fragsfw=pass out quick on pppoe0 proto icmp all keep state keep frags; incoming trafficfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 21 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 23 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state ; icmp trafficfw=pass in quick on pppoe0 proto icmp all keep state; other will be blockedfw=block in log quick on pppoe0 allfw=block out log quick on pppoe0 all[dhcpd]; Global dhcp parametersallow unknown-clients;ddns-update-style none;; Parameter for the Subnetsubnet 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;
CONFIGURATION FILESCHAPTER 559iGATE 15.0. Revised: 2009.5.1.11.4 VLAN SCENARIOIn the following example, the system is connected to the IP backbone through emac0. One Computer is connectedto the emac1 interface. You can separate voice and data traffic with two different VLANs (vlan0 with tag 10 forvoice, vlan1 with tag 11 for data). All traffic coming from emac1 will be sent to vlan1. Voice and data will not bemixed: 5.2 CONFIGURATION FILE PABX.CFGThe pabx.cfg file contains system-specific settings and the port configuration. It is divided into the [System] and[Night<num>] sections.5.2.1 SYSTEM SETTINGSThe [System] section is divided into several categories to ensure clarity. Life line (relay)Log filesNight configurationControllersSubscribersGlobal settingsSMTP-client configurationNumber portability settingsThe following subchapters contain a detailed description of these categories.5.2.1.1 LIFE LINEThe entry in this category is responsible for the life-line (bypass) functionality of the PRI port’s relay when the systemis on. When the system is off, both PRI ports are connected to each other, which means that it provides a trans-parent connection between the PBX and the PSTN. When the system is on, all routing algorithms are active.Bypass=ON/OFF[System][emac0]IpAddress=192.168.1.12/16[emac1]IpAddress=up[vlan0]IfConfig=vlan 10,7 vlanif emac0IpAddress=10.0.1.2/24[vlan1]IfConfig=vlan 11,1 vlanif emac0IpAddress=172.16.4.5/16[bridge0]BrConfig=add vlan1 add emac1 up
CONFIGURATION FILESCHAPTER 560iGATE 15.0. Revised: 2009.ON: PRI relay is on (system controls both PRI ports).OFF: PRI relay is off (both PRI ports are connected to each other, regardless of whether or not the system is run-ning). 5.2.1.2 LOG FILESCDRs, unconnected calls, system events, trace output and statistics can be saved into files.The following entries are necessary to generate log files: The path in the example refers to an optional external flash disk. If there is no external flash disk, the path will be:boot.Example:ActionLog=/boot/protocol.log You can define how the log files are to be divided. There are two possibilities for saving entries into a new file:In increments of time (twice-daily, daily, weekly, monthly)Depending on the size of the fileYou can also define a maximum number of up to 35 files to be generated.To ensure bypass functionality, make sure this parameter is always set to ON.Table 5.9 pabx.cfg: Log File Entries Entry DescriptionActionLog=/data/protocol.log System eventsLog=/data/cdr.log CDR entriesfailedlog=/data/failed.log Unconnected callsTraceLog=/data/trace.log System traceMsgLog=/data/msg.log Incoming SMS and USSD messagesThe available internal memory is approximately 8 MB if the iGATE does not contain optional memory expansion. Make sure you monitor the available memory.iiii
CONFIGURATION FILESCHAPTER 561iGATE 15.0. Revised: 2009.A dash (-) appears in place of information that is to be ignored.Example 1 In the following entry, the files cdr.log and failed.log are renamed every day or whenthe file reaches 180kB, whichever comes first. Up to 7 CDR files will be saved on the system. Ifthe file size reaches 180kB on one day, the second file will have the same date. Only the runningnumber will be increased. Example 2 In the following entry, the file protocol.log is renamed every day or when the file reaches 60 kB.Up to 21 failed files will be saved on the system. Example 3 In the following entry, the file trace.log is renamed every day when the file has reached600kB. Up to seven log files will be saved on the system.Example 4 In the following entry, the statistic values are reset daily at 12:00 midnight and saved in theasr.log.Table 5.10 pabx.cfg: Log Parameters Log=/data/<file.log> <saved> <size> <number><file> The name of the log file is generated as follows: [file]yymmdd[0-9|A-Z].log.<saved> Refers to the frequency with which the file is saved. The following options are possible:halfdaily Every day at 11:59 and 23:59daily Every day at 23:59weekly Sunday at 23:59monthly The last day of the month at 23:59<size> Regardless of the value entered in <saved>, the file will be saved when the <file size> has been reached (in kB).NOTE: We recommend a file size of a multiple of 60kB.<number> 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.Log=/data/cdr.log daily 180 7failedlog=/data/failed.log daily 180 7ActionLog=/data/protocol.log daily 60 21TraceLog=/data/trace.log daily 600 7StatisticTime=/data/asr.log 00:00 11111111
CONFIGURATION FILESCHAPTER 562iGATE 15.0. Revised: 2009.5.2.1.3 NIGHT CONFIGURATIONThe 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 NightRe-setTime 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 aholiday:The configuration section switches back to the default configuration (System section) every day at 8:00 p.m:NightResetTime=20:00 11111111HolidaysUp to 50 different dates can be set for night sections used by holiday. The variable dd.mm sets the day and monthin which the night section is activated when the 8th bit is set in the bitmask (see Table 5.11 >).Please remember to keep track of how much memory is available on the system.Table 5.11 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 at that time on the defined day. <day> Use a bitmask to set the weekdays on which the configuration applies here. The daymap appears in the following order: HoSaFrThWeTuMoSu.Night2=12:00 00101010ii
CONFIGURATION FILESCHAPTER 563iGATE 15.0. Revised: 2009.5.2.1.4 CONTROLLERSThis category defines the parameters that apply to the ports. The order of the ports is defined as follows: The iGATEcontains integrated iGATE 4 Mobile Boards, each of which contain four mobile modules. EachiGATE 4 Mobile Board’s mobile channels are configured as additional controllers. That means four controllers areconfigured for each board. Beginning with 0, these controllers are defined as the first controllers in the section.Next the PRI controllers are defined, followed by the VoIP controllers. All controllers are defined in ascending order. Table 5.12 > describes the order for additional boards.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.5 on page 80 >). 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 81 >).Table 5.12 Configuration Order: Controller ParametersFunction Number of ControllersiLCR 4BRI BoardsUp to 4 (optional)iGATE 4 Mobile BoardsUp to 32 (optional)iLCR Base Board (PRI) 2iLCR Base Board (VoIP) Up to 4 (optional)DTMF (virtual) Up to 1 (optional)Table 5.12 > shows only the maximum number of controllers for each individual in-terface. Any possible combinations will depend on the system’s specifications! iiii
CONFIGURATION FILESCHAPTER 564iGATE 15.0. Revised: 2009.The individual ports are defined with the following parameter: Table 5.13 pabx.cfg: Controller Parameters Controller<port>=<bus> <type> <mode> <line_type> ADR:<address> IRQ:<interrupt> UNIT: VALUE:<port> Defines the running (physical) port number.<bus> Defines the configured (virtual) port number. In the default configuration, PRI TE ports are 9 and PRI NT ports are 10. VoIP ports are 40.<type> Defines the connection type:TES2M PRI external (terminal endpoint)NTS2M PRI internal (network termination)VOIP VoIP moduleGSM GSM portCDMA CDMA portUMTS UMTS portTE BRI external (if you change from NT to TE or vice versa, you must change the DIP switches for the respective port on the iLCR 4BRI Board)NT BRI internal DTMF virtual controller for activating DTMF tone recognition<mode> Defines the protocol variation for PRI and BRI lines:DSS1 CASR2 (only for PRI lines)<line_type> Switches CRC4 mode for PRI lines on or off:CRC4 CRC4 onDF double frame: CRC4 offAdditional entry for T1 only:T1 US Defines this controller as T1. Bear in mind that if one controller is defined as T1, all controllers must be thus defined. If you configure T1, you must also enter CHMAX[23] in the corresponding Subscriber lines.T1 EXAMPLE:MULAW=YesController00=20 TES2M DSS1 T1 US Controller01=21 NTS2M DSS1 T1 US...Subscriber00 = TRANSPARENT ROUTER CHMAX[23]Subscriber01 = TRANSPARENT ROUTER CHMAX[23]<address> (Optional) Defines the hardware address used for the first controller on an additional iGATE 4 Mobile Board. These entries are preconfigured and cannot be changed.
CONFIGURATION FILESCHAPTER 565iGATE 15.0. Revised: 2009.Ports set to the same type can have the same bus number. In this case they will form a trunk group. If you changethis parameter in the configuration, you must restart the system.Example 1 Each iGATE 4 Mobile Board contains 4 controllers. The hardware address and the interrupt aredefined behind the first controllers, which are defined in the configuration before the iLCRBase Board. In the following example, the system contains four iGATE 4 Mobile Boards. One PRIcontroller is configured for TE and one for NT. The protocol used is DSS1, and CRC4 is active. OneVoIP Module is attached. <interrupt> (Optional) Defines the interrupt used for the first controller on an additional iGATE 4 Mobile Board. These entries are preconfigured and cannot be changed.UNIT: (Optional) Defines the currency for the charges (default EUR). Special charge generation is possible. Special charge generation is possible for:France UNIT:&FSpain UNIT:&SPPortugal UNIT:&PGreece UNIT:&GSwitzerlandUNIT:&CHNetherlandsUNIT:&NLItaly UNIT:&INOTE: The <line_type> must be configured for these entries to work. EXAMPLE: Controller02=10 NT DSS1 PMP UNIT:€ VALUE:0.010Controller03=10 NT DSS1 PMP UNIT:€ VALUE:0.010VALUE: (Optional) Defines the charges that accumulate by unit (default 12).DSP:6 Specific SIP features are converted to ISDN information elements and vice versa. This set-ting will change the codeset for the display element from 0 (default) to 6. That is used to avoid configuration changes at the PBX: In the following example, the display IE at controller 1 is sent in the codeset 6:Controller01 = 9 TES2M DSS1 DSP:6Table 5.13 pabx.cfg: Controller Parameters (continued)Controller<port>=<bus> <type> <mode> <line_type> ADR:<address> IRQ:<interrupt> UNIT: VALUE:
CONFIGURATION FILESCHAPTER 566iGATE 15.0. Revised: 2009.Example 2 Each iGATE 4 CDMA Board contains 4 controllers. The hardware address and the interrupt aredefined behind the first controllers. These are defined in the configuration before the optionaliLCR 4BRI Board. The hardware address and the interrupt for this board is also defined behindits first controller. The last controllers are for the iLCR Base Board. In the following example, thesystem contains 2 iGATE 4 CDMA Boards, a iLCR 4BRI Board with 4 controllers. One PRI control-ler is configured for TE and one for NT. The protocol used is DSS1, and CRC4 is active. Example 3 Each iGATE 4 UMTS Board contains 4 controllers. The hardware address and the interrupt are de-fined behind the first controllers, which are defined in the configuration before the iLCRBase Board controllers. In the following example, the system contains 2 iGATE 4 UMTS Boards.One PRI controller is configured for TE and one for NT. The protocol used is DSS1, and CRC4 isactive. One VoIP Module is attached.Controller00=20 GSM ADR:D800 IRQ:5 Controller01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSM ADR:D900 IRQ:7 Controller05=20 GSMController06=20 GSMController07=20 GSMController08=20 GSM ADR:DA00 IRQ:5Controller09=20 GSMController10=20 GSMController11=20 GSMController12=20 GSM ADR:DB00 IRQ:7Controller13=20 GSMController14=20 GSMController15=20 GSMController16=9 TES2M DSS1 CRC4Controller17=10 NTS2M DSS1 CRC4Controller18=40 VoIPController00=30 NT DSS1 PMP ADR:C000 IRQ:11 Controller01=30 NT DSS1 PMP Controller02=30 NT DSS1 PMP Controller03=30 NT DSS1 PMP Controller04=20 CDMA ADR:D800 IRQ:5Controller05=20 CDMAController06=20 CDMAController07=20 CDMAController08=20 CDMA ADR:D900 IRQ:7Controller09=20 CDMAController10=20 CDMAController11=20 CDMAController12=9 TES2M DSS1 CRC4Controller13=10 NTS2M DSS1 CRC4Controller00=20 UMTS ADR:D800 IRQ:5Controller01=20 UMTSController02=20 UMTSController03=20 UMTSController04=20 UMTS ADR:D900 IRQ:7Controller05=20 UMTSController06=20 UMTSController07=20 UMTSController08=9 TES2M DSS1 CRC4Controller09=10 NTS2M DSS1 CRC4Controller10=40 VoIP
CONFIGURATION FILESCHAPTER 567iGATE 15.0. Revised: 2009.5.2.1.5 SUBSCRIBERSVarious functions for individual interfaces (ISDN or VOIP) are defined in each controller’s Subscriber line. Theorder of the subscriber lines is the same as the order of the controller lines (see Chapter 5.2.1.4 on page 63 >).Most changes become active following a restart. If it suffices to activate the configuration, this is noted in the pa-rameter description: Additional parameters for mobile controllers are described in Table 5.15 > and Table5.16 >. The parameters listed in Table 5.15 > are required for mobile controllers and those listed in Table5.16 > are optional, depending on the implementation scenario.Required Mobile ParametersSpecific settings for each mobile interface appear in square brackets behind the keywords GSM, UMTS or CDMA.These parameters are separated with a comma.Table 5.14 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. No other parameters in this table are set.TRANSPARENT ROUTER Only the number is sent as caller ID (without the virtual port address). Activate configuration suffices to activate changes.CASR2[<name>] Activates the profile defined in the corresponding [CASR2] section.ALARM Activates the monitoring mode for the respective port. If a relevant error occurs at the port, a remote call is placed to the number defined in RemoteCallBack. Activate configuration suffices to activate changes.SWITCH Changes internal port handling. In the default configuration, the VoIP control-ler is set to NT. You can use this parameter to change it from NT to TE. Restart the system to activate the changes.CHMAX[xx] Defines the number of channels per VoIP controller (VoIP Module), e.g. 16 or for the virtual DTMF controller. This figure must be entered in double digits. A maximum of six concurrent channels are possible for DTMF recognition.NOTE: If all six channels are used, no PPP dialup or remote access via ISDN is possible.DTMF[<sec>,/<dir>/<file>] Please refer to Chapter 11.2.1.1 >.
CONFIGURATION FILESCHAPTER 568iGATE 15.0. Revised: 2009.The following parameters are required: Table 5.15 Required Parameters in pabx.cfg Subscriber<port>=<type>[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM<x>,...]<port> Defines the running (physical) port number.<type> Defines whether a GSM, CDMA or UMTS module is used.<pin> Defines the SIM card’s PIN. The PIN is always four digits. If no PIN is defined for a SIM card, the PIN 0000 must be used.NOTE: An error message appears in the protocol.log file when a PIN is in-correctly configured.<lain> Defines the LAIN (Local Area Identification Number) – the mobile network to be used. This prevents roaming into another mobile network. The LAIN is always five digits. If the LAIN is set at 00000, roaming will not be prevented. The LAIN configuration prevents accidental logon of the SIM card with another network and the use of false SIM cards.<SMSC> Defines the SMS center’s access number. The number must always begin with + and the country code.<SIM> Defines the SIM card to be used. You can enter the values 1, 2, 3, 4, 5, 6 (optional when using the 24 SIM card carrier). Default 1. Do not change the default entry if you use the parameter SIM4 or SIMS. Activate configuration suffices to activate changes.NOTE: Please see the example following Table 5.16 > for information on numbering SIM cards.
CONFIGURATION FILESCHAPTER 569iGATE 15.0. Revised: 2009.Optional Mobile ParametersIn addition to the usual parameters, you can enter the following optional mobile parameters. Separate each pa-rameter with a comma. <loudGSM> Defines the volume level for the mobile line. The values 0 to 3 are possible. 0 is loudest and 3 is the least loud.Activating echo cancellation (for GSM modules only):Depending on the base station (BTS) one of three algorithms will work for this feature. The algorithms must be tested during activation to determine which one fits the base station type.The following values are added to the volume setting:- 16 -> algorithm 1 - 32 -> algorithm 3 - 48 -> algorithm 6 EXAMPLE 1: If the volume level is set at 1, and algorithm 1 is used for echo cancellation, the configuration for <loudGSM> is 17:Subscriber00=… GSM[0000,00000,+000000,1,17,1,SIM4] …EXAMPLE 2: If the volume level is set at 2, and algorithm 6 is used for echo cancellation, the configuration for <loudGSM> is 50:Subscriber00=… GSM[0000,00000,+000000,1,50,1,SIM4] …<loudPCM> Defines the volume level to the fixed network. The values 0 to 7 are possible. 7 is loudest and 0 is the least loud.SIM4 Defines the SIM-card carrier used. The number entered (4) refers to the number of slots. The SIM-cards can be distributed among the 4 mobile channels at will.NOTE: This parameter cannot be used in combination with SIM24 or SIMS.SIM24 Defines the SIM-card carrier used. The number entered (24) refers to the number of slots. The SIM-cards can be distributed among the 4 mobile channels at will.NOTE: This parameter cannot be used in combination with SIM4 or SIMS.Table 5.16 Optional Parameters in pabx.cfg Optional Mobile ParametersIMSIThis keyword causes the IMSIs to be recorded in each CDR. This parameter appears after SIM<x>. Activate configuration suffices to activate changes.Table 5.15 Required Parameters in pabx.cfg (continued)Subscriber<port>=<type>[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM<x>,...]
CONFIGURATION FILESCHAPTER 570iGATE 15.0. Revised: 2009.SIMSDefine this keyword to connect the system to a vGATE. <sim> must be set to 1 in the appropriate mobile controller Subscriber line. NOTE: This parameter cannot be used with the following parameters: SIM24 or SIM4. Bear in mind that no SIM-card carrier is to be inserted in the iGATE.EXAMPLE: Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIMS]BAND(<int>)For iGATE 4 UMTS Boards with module type MC8755V only:Defines the mobile standard used and (<int>) can have the following values: 0 = autonegotiation (default)1 = UMTS3 = GSMFor GSM modules:Defines the GSM frequency band and (<int>) can have the following values:1 = Mono-band mode 850MHz (Q24CL001 modules only)2 = Mono-band mode 900MHz (Q24CL001 modules only)3 = Mono-band mode 1800MHz (Q24CL001 modules only)4 = Mono-band mode 1900MHz (Q24CL001 modules only)5 = Dual-band mode 850/1900MHz (Q24CL001 and GE864-QUAD modules)6 = Dual-band mode 900/1800MHz (Q24CL001 and GE864-QUAD modules)7 = Dual-band mode 900/1900MHz (Q24CL001 and GE864-QUAD modules)8 = Dual-band mode 850/1800MHz (GE864-QUAD modules only)After changing the band settings, you must restart the system to activate the changes.NOTE: The BAND parameter can only be used with quad-band GSM module-type Q24CL001. These quad-band GSM modules are available as of hardware revision 1.61 (May, 2007). There is no default band setting! If there is no BAND configuration in the pabx.cfg when the system is started, the last band stored on the module will be used. This can cause the system to attempt to register the SIM with the wrong GSM band.BNDS<int>For iGATE 4 UMTS Boards with module type UC864-G only:Selects the UMTS or GSM or auto network0 = auto (default)1 = GSM2 = UMTS Table 5.16 Optional Parameters in pabx.cfg (continued)Optional Mobile Parameters
CONFIGURATION FILESCHAPTER 571iGATE 15.0. Revised: 2009.BNDU<int>For iGATE 4 UMTS Boards with module type UC864-G only:Configures BAND selection in the UMTS network0 = 850/1900/2100 MHz (default)1 = 850 MHz2 = 1900 MHz3 = 2100 MHzEVL(<int>)For GSM module type Q24CL001 only:Specifies the switch’s maximum attenuation. 0 = 31 db (default)1 = 29 db2 = 27 db3 = 25 db...15=1 dbThis option is available when echo cancelation 17 is defined in loudGSM.EXAMPLE:Subscriber12 = TRANSPARENT ROUTER GSM[0000,00000,+49111111,1,17,1,SIM4,IMSI,EVL(10),EST(1)] ALARMEST(<int>)For GSM module type Q24CL001 only:Specifies the interval between attenuation and no attenuation. 0 = 1 db 1 = 2 db2 = 3 db3 = 4 db (default)This option is available when echo cancelation 17 is defined in loudGSM.EXAMPLE:Subscriber12 = TRANSPARENT ROUTER GSM[0000,00000,+49111111,1,17,1,SIM4,IMSI,EVL(10),EST(1)] ALARMETR(<int>)For GSM module type Q24CL001 only:Enter a value between 0 and 31 (default 10) to define the relative threshold between maximum and mini-mum energy information. This option is available when echo cancelation 17 is defined in loudGSM. Table 5.16 Optional Parameters in pabx.cfg (continued)Optional Mobile Parameters
CONFIGURATION FILESCHAPTER 572iGATE 15.0. Revised: 2009.Example: The following example has two groups of SIMs. Different SMS center numbers are set for con-trollers 00-07 and 08-15. SIM 24 Carriers are used, so that several SIMs can be used for eachmobile channel. SIM-position 1 is used in the SIM 24 Carrier for the first, third and fourthiGATE 4 Mobile Board (SIM-slots 0-3). SIM-position 2 is used in the secondiGATE 4 Mobile Board SIM-slots 4-7). Routing to mobile is based on the LAIN (CHADDR): ETM(<int>)For GSM module type Q24CL001 only:Enter a value between 0 and 31 (default 7) to define the threshold of maximum energy information. This option is available when echo cancelation 17 is defined in loudGSM. Subscriber00 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIM24,IMSI] CHADDR ALARM NEXTSubscriber01 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIM24,IMSI] CHADDR ALARM Subscriber02 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber03 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber04 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,2,1,1,SIM24,IMSI] CHADDR ALARMSubscriber05 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,2,1,1,SIM24,IMSI] CHADDR ALARM Subscriber06 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,2,1,1,SIM24,IMSI] CHADDR ALARMSubscriber07 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,2,1,1,SIM24,IMSI] CHADDR ALARMSubscriber08 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARM NEXTSubscriber09 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARM Subscriber10 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber11 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber12 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber13 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARM Subscriber14 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber15 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIM24,IMSI] CHADDR ALARMSubscriber16 = TRANSPARENT ROUTER ALARMSubscriber17 = TRANSPARENT ROUTER ALARMSubscriber18 = TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMFor a detailed description of the configuration of the iGATE 4 Mobile Board, includ-ing the keywords CHADDR, NEXT, LIMIT and CONTINUE, please refer to Chapter 7 on page 101 >.Table 5.16 Optional Parameters in pabx.cfg (continued)Optional Mobile Parametersii
CONFIGURATION FILESCHAPTER 573iGATE 15.0. Revised: 2009.5.2.1.6 GLOBAL SETTINGSThis category contains the following system parameters: Table 5.17 pabx.cfg: IP Configuration System Parameters System ParametersVoipGlobalMaxChan=<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). A different port for sending can be set in the route.cfg’s VoIP profile. Oth-erwise the port set here will be used for sending and receiving.VoipMaximumBandwidth=<int>Defines an upper limit for available bandwidth for the VoIP profiles to be configured (see VoipBand-widthRestriction in Table 9.6 >) if traffic shaping is active for the corresponding VoIP profile. Individual co-decs are assigned the following values:g711a, f711u, trp: 8g72632, t38: 4g72624 3g72616, gsm 2Other 1You 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.VoipLinger=<sec>After an H.323 release complete has been sent, the TCP session will remain open for the number of seconds entered if there is no response from TCP message sent so that the system can resend the TCP packet.
CONFIGURATION FILESCHAPTER 574iGATE 15.0. Revised: 2009.StunServerAddress=<ip addr>When this parameter is active, the iGATE 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 Voip-GlobalMaxChan 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 ISP’s DNS server. If you don’t know it, you can also enter another DNS server. If you have more than one address, enter this parameter up to three times on different lines.Timezone=<continent/city>Defines the time difference between the iGATE’s 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 iGATE’s 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=...TIMEClockmaster=<type>Enter S0 to take the system clock from the BRI port if the system has an additional BRI board and special firmware installed on which at least one controller is connected to the PSTN in TE mode. This parameter only makes sense if the system does not have a PRI port connected to the PSTN.S2MLongHaul=<mode>This option increases the sensitivity on PRI receiving side to support Long Haul applications. The default value is No (Short Haul).Table 5.17 pabx.cfg: IP Configuration System Parameters (continued)System Parameters
CONFIGURATION FILESCHAPTER 575iGATE 15.0. Revised: 2009.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).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) TFTP access. Default off.RemotePassword=<password>Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.12.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 5.17 pabx.cfg: IP Configuration System Parameters (continued)System Parameters
CONFIGURATION FILESCHAPTER 576iGATE 15.0. Revised: 2009.Example:SimCtrlUnitAddress=<ip addr>Enter the vGATE Control Unit’s IP address. For a detailed description of iGATE configuration for connection to a vGATE, see Chapter 7.1 >.SimCtrlUnitCheckInterval=<sec>The iGATE will send a keep alive to the vGATE Control Unit in the check intervals set here (no default value, not executed if not set).SimCtrlUnitMinRSSIInterval=<sec>The Received Signal Strength Indication is sent with a minimum interval of 60 seconds per controller. Use this parameter to change the value in seconds.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 carrier’s 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:GEDEIRUKUSFRITVoipGlobalMaxChan=60H225Port=1720SipPort=5060VoipRtpPort=29000VoipRtpPortSpacing=2NameServer=192.168.0.254Timezone=Europe/BerlinNtpServer=192.168.0.254DialTone=GETable 5.17 pabx.cfg: IP Configuration System Parameters (continued)System Parameters
CONFIGURATION FILESCHAPTER 577iGATE 15.0. Revised: 2009.5.2.2 SMTP-CLIENT CONFIGURATIONThe following entries in the pabx.cfg’s [Mail] section are used to send e-mail messages from the iGATE. The con-nection to the SMTP server can be used to send CDR files, incoming SMS to an e-mail account or alarm messages.The following features are possible:Sending SMS via e-mailReceiving SMS in an e-mail, SMS or in a fileSending and receiving USSD text messagesDisplaying incoming calls via e-mailSetting up connections using e-mailSending automatic SMS for unconnected callsSending CDRs via e-mailSending alarm messages via e-mailThere 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 or PRI, a clock may come from the network connected to the cor-responding port. Enter !TIME in the pabx.cfg’s subscriber line and then activate the configuration to block this clock.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.iiii
CONFIGURATION FILESCHAPTER 578iGATE 15.0. Revised: 2009.MailPortIn=<num>Enter a TCP port for incoming email (default 25).MailPortOut=<num>Enter a TCP port for outgoing email (default 25).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.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. Default 4MailToHostRetries=<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. Default 10.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 100.
CONFIGURATION FILESCHAPTER 579iGATE 15.0. Revised: 2009.Example:Sending Alarm Messages via E-mailWith the appropriate configuration, you can send e-mails containing alarm messages that are written into the logfile. The sender is given as alarm and the system’s name appears in the subject box. The text box contains thealarm message. The following entry in the configuration file activates this function: 5.2.3 NUMBER PORTABILITY SETTINGSThe [NumberPortability] section includes the parameters necessary for communication with the database server.For a description of the functionality and configuration of this feature, please see Chapter 11.6 >.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.[Mail]SmtpServer=172.16.0.10MailRcpt=teles.deMailFrom=172.16.0.100MailRcvMax=300MailRcptMax=50MaxMailsToHost=2MailToHostRetries=10MailSendRetries=10MailAllowedPeers=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.ii
CONFIGURATION FILESCHAPTER 580iGATE 15.0. Revised: 2009.Example:5.2.4 SNMP SETTINGSThe Simple Network Management Protocol facilitates network management and monitoring of iGATE network de-vices and their functions. For a detailed description of SNMP configuration, please refer to Chapter 12.3 >.5.2.5 TIME-CONTROLLED CONFIGURATION SETTINGSThe [Night<num>] section is reserved for prospective time-controlled configuration changes. In the pabx.cfgfile, the Night sections contain all of the system’s Subscriber entries.MNPQAddress=<ip addr>Enter the IP address to which the number portability query is to be sent. The service comes from an external provider. It is also used as the iMNP address if the parameter MNPQSum=Yes is set.MNPQPort=<port>Enter the port to which the number portability query is to be sent.MNPQAddress2=<ip addr>Enter the IP address to which the second number portability query is to be sent when ! appears in the map-ping entry. A second database will then be queried, for example if the first on is not online.MNPQPort2=<port>Enter the port to which the second number portability query is to be sent.MNPQSum=<mode>This parameter must be activated (Yes) if a iMNP is used.E2EMRSAddress=<ip addr>Enter the IP address to which the number portability query is to be sent. The service comes from an external provider.E2EMRSPort=<port>Enter the port to which the number portability query is to be sent. [NumberPortability]MNPQAddress=172.16.0.100MNPQPort=9003MNPQSum=YesYou must restart the system after making changes to activate the settings.ii
CONFIGURATION FILESCHAPTER 581iGATE 15.0. Revised: 2009.Individual SIM-card positions can be configured here. For a detailed description of time-controlled SIM switching,please refer to Chapter 7.10 >5.2.6 .CASR2 SETTINGSIf you are working with Channel Associated Signaling, you must activate a CAS profile in the relevant Control-ler and Subscriber entries and define a profile for each Subscriber entry in a separate[CASR2:<name>] section. Generally you will need to set only the country code 55 for Brazil. The default country code is 0, which sets the ITU-T standard. Example:5.3 CONFIGURATION FILE ROUTE.CFGThe system’s routing information is saved in the route.cfg. The file contains the following sections: [System]Contains all routing entries (MapAll, Restrict, Redirect) that are to be active when the default configurationis used.[Night<num>]Contains all routing entries (MapAll, Restrict, Redirect), and VoIP, gatekeeper and registrar profiles thatare to be active with the defined time configuration. Bear in mind that you must also copy all routing andprofile settings that may already appear in the das System section or in the individual profile sections, evenif they do not change![VoIP:<name>]Contains all settings necessary for communication with the VoIP peer.[GateKeeper:<name>]Contains all settings for the gatekeeper. This profile is then assigned to the VoIP profiles.[Registrar:<name>]Contains all settings to register with the registrar.Controller00=9 TES2M CASR2...Subscriber00 = TRANSPARENT ROUTER CASR2[BRAZIL1] ALARMSubscriber01 = TRANSPARENT ROUTER CASR2[BRAZIL2] ALARM...[CASR2:BRAZIL1]CountryCode=55[CASR2:BRAZIL2]CountryCode=55You must restart the system after making changes to activate the settings.ii
CONFIGURATION FILESCHAPTER 582iGATE 15.0. Revised: 2009.5.3.1 ENTRIES IN THE [SYSTEM] SECTIONThe[System]section contains the following entries.5.3.1.1 MAPPINGMapping entries begin with the keyword MapAll. Example: In the following example, all mobile calls with the prefix 01555 are transmitted to the mobilecontrollers (20). All international calls are sent to the VoIP carrier (40) with the profile nameDF. All national calls are sent to the PRI controller with the number 9: If CHADDR appears in the mobile port’s Subscriber lines, the entry will look like this:MapAll<num>=<lain><num>Example: In the following example, all calls with the prefixes 01555 and 01556 are sent to the mobile con-trollers with the LAIN 26212. All calls with the prefixes 01444 and 01445 are sent to the mobilecontrollers with the LAIN 26213. Digit collection is activated:Table 5.18 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 port’s 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 to appear on the rightThe 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.MapAll01555=|2001555<<14MapAll00=40DF:00MapAll0=90MapAll01555=|2621201555<<17MapAll01556=|2621201556<<17MapAll01444=|2621301444<<17MapAll01445=|2621301445<<17
CONFIGURATION FILESCHAPTER 583iGATE 15.0. Revised: 2009.5.3.1.2 RESTRICTThis entry is for controller-specific routing entries. These entries apply only for a single controller and can be set foran OAD base number or an MSN: Make sure that the numbers for the carriers are routed to the correct ports! For de-tailed information on digit collection and enblock/overlap receiving, see Chapter 8.1 >.Table 5.19 route.cfg: Restrict Parameters Restrict<ns>=<pl> <sin><ns> Defines the virtual controller number plus an optional base number or a specific calling number. <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 a service. Without a sin, the Restrict command is valid for all services.Possible service indicator values are:00 All services01 Telephony02 Analog services03 X.21-services04 Telefax group 405 64 kbps videotext or TELES-specific SMS services06 TELES-specific USSD services07 Data transfer 64 kbps08 X.25-services09 Teletext 6410 Mixed mode15 Videotext (new standard)16 Video telephone<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>.ii
CONFIGURATION FILESCHAPTER 584iGATE 15.0. Revised: 2009.Example: In the following example, all calls from PRI controller 9 (PSTN) are sent to PRI controller 10 (PBX)without regard to the routing file: Example: In the following example, calls from mobile controllers with the LAIN 26212 are sent to PRI con-troller 10 (PBX), extension 0. This is imperative, since the caller cannot dial an extension directlywith mobile:For a detailed description, see Chapter 7.4 >.5.3.1.3 REDIRECTThis 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 placeholderentered:Restrict9=plMapAllpl=10Restrict and Redirect values cannot be the same on the left side of the equal sign. Scenarios that are to perform as if both values were on the left side require more specific routing entries. In the following example, the calling-party number for incoming GSM calls must al-ways appear in the international format. Outgoing GSM calls must begin with the do-mestic long-distance prefix.redirect326211=new_routerestrict262110049=inMapAll0=262110Restrict26212=100This function requires the LCR license.When the Restrict and Redirect values on the left side of the equal sign are the same, Redirect must appear above Restrict as in the following example:redirect326211=new_routerestrict26211=iniiii
CONFIGURATION FILESCHAPTER 585iGATE 15.0. Revised: 2009.Example: In the following example all mobile calls with the prefix 01555 are transmitted to the mobile car-rier with the LAIN 26212. Digit collection is activated. If the carrier cannot be reached or is busy,the redirect command activates the second target mapping with the placeholder A and the callis automatically sent to PRI controller 9.Table 5.20 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 answer3 call forwarding when busy5 call forwarding when busy and no answer<num> Defines the number for which calls will be redirected. <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 Restrict command is valid for all services.Possible service indicator values are:01 Telephony02 Analog services03 X.21-services04 Telefax group 405 Videotext (64 kbps)07 Data transfer 64 kbps08 X.25-services09 Teletext 6410 Mixed mode15 Videotext (new standard)16 Video telephoneNOTE: Fax forwarding must be set for analog and telephony services be-cause incoming fax calls from the analog network may arrive with either telephony or analog service indicators.<time> Enter a number of seconds between 1 and 60. For type 2 only.MapAll01555=|2621201555<<17Redirect326212=AMapAllA=9
CONFIGURATION FILESCHAPTER 586iGATE 15.0. Revised: 2009.Excluding Busy Calls or Specific Cause Values from RedirectDefines a hexadecimal cause value according to DSS1. When connections to the destination are rejected becauseof the reason defined by the cause value, the iGATE sends a busy signal to the attached PBX. Alternative routingis not carried out.To avoid second-choice routings when the called-party number is busy, set the following parameter in the first-choice port’s Subscriber line in the pabx.cfg:Example: In the following example, all outgoing calls over controller 04 are rejected with the cause value91 when the called party is busy. Alternative routing is not carried out.5.3.1.4 SETTING THE TIME-CONTROLLED SECTIONSIf you use a time-configured route on the system, please see Chapter 5.2.1.3 > for a definition of individual con-figuration zones. The active route is configured in the route.cfg file.The following example contains three sections ([System], [Night1] and [Night2]), in which the route changes. Allinternational calls are sent to the VoIP carrier DF in the default configuration. Digit collection is actived. In the timespan for [Night1], these international calls are routed to VoIP carrier Ni, and in the time span for [Night2] they arerouted through the PRI controller to the carrier with the prefix 010xx. National calls are always sent to VoIP carrierDF and local calls are routed to the outside line.Example: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 iGATE sends a busy signal to the attached PBX. Alternative routing is not carried out. You can also define a range of consecutive cause values: BUSY[<cause>,<cause>]An exclamation point (!) in front of a cause value means all cause values except the one listed. For example, BUSY[!95], means all cause values except 95 will be rejected with a busy signal.Subscriber04=....BUSY[91][System]MapAll00=|40DF:00<<24MapAll0=|40DF:0<<24MapAll?=9?[Night1]MapAll00=|40Ni:00<<24MapAll0=|40DF:0<<24MapAll?=9?[Night2]MapAll00=9010xx00MapAll0=|40DF:0<<24MapAll?=9?
CONFIGURATION FILESCHAPTER 587iGATE 15.0. Revised: 2009.5.3.2 VOIP PROFILESThis section includes all of the most important parameters for communication with the VoIP peer.Basic ParametersAny defined Night configurations 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.5 on page 80 >). The active route must appear in the route.cfg (see Chapter 5.3 on page 81 >).Table 5.21 route.cfg: VoIP Basic Parameters VoIP Basic Parameters[Voip:<name>]Name of the routing profile. The name must begin with a letter. Use a short and meaningful name.VoipDirection=<mode>Defines the direction in which VoIP calls can be set up. Possible options: In, Out, IO, None).VoipPeerAddress=<ip addr> or <name>The peer’s IP address or name. Default is 0 (if it is not set, please set the parameter VoipIpMask to 0x00000000).VoipIpMask=<ip mask>The subnetmask is used to determine the size of the IP address range for incoming traffic. The syntax is 0x followed by the mask in hexadecimal notation. Example of a Class C mask entry: 0xffffff00. Default is 0xffffffff (only incoming traffic is accepted from the defined peer address).VoipSignalling=<int>Determines the profile’s signaling protocol for outgoing VoIP calls. In the case of incoming calls, 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.ii
CONFIGURATION FILESCHAPTER 588iGATE 15.0. Revised: 2009.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, g729abThese 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, g72632These 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.g728The Codec has a bit rate of 16kBit/s (compression ratio 1:4).g711a, g711uThese PCM codecs have a bit rate of 64kBit/s. No voice compression occurs. a stands for a-law and u for µ-law. g723, g723LThese 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.gsmGSM-FR (full rate) has a bit rate of 13 kbit/s. The following codecs are also possible: g721 (SIP only)Fax: t38T.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: Clear channel codecccd: Clear channel data (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.21 route.cfg: VoIP Basic Parameters (continued)VoIP Basic Parameters
CONFIGURATION FILESCHAPTER 589iGATE 15.0. Revised: 2009.Please refer to Chapter 9 > for information on other possible entries.Management ParametersVoipMaxChan=<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 activates silence suppression, CNG (comfort noise generation) and VAD (voice activity detection). No (de-fault) deactivates silence suppression. NOTE: In SIP signaling, silence suppression is negotiated as per RFC3555.VoipTxM=<num> or <list> fixThe multiplication factor (1-12) for the frame size for transmission of RTP packets (default is 4). 10ms is the default frame size (20ms for iGATE32). A list can be defined if different frame sizes are to be used for different codecs in the VoIP profile. The list must correspond with the list in the parameter VoipCompression.Normally the peer’s frame size will be used if it is smaller than the one defined. If you enter fix, the configured factor will always be used. Table 5.22 route.cfg: VoIP Management Parameters VoIP Management ParametersVoipGk=<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.Table 5.21 route.cfg: VoIP Basic Parameters (continued)VoIP Basic Parameters
CONFIGURATION FILESCHAPTER 590iGATE 15.0. Revised: 2009.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. If the call is sent to the mobile network, the SIM card’s IMSI is transferred in the Vendor attribute: Vendor-2170-Attr-1 = in hexadecimal notation in the fol-lowing format: IMSI=<IMSI>VoipRadiusIMSINegotiation=<mode>If yes is entered, the <system> will negotiate the IMSI to be used in the Radius access request. It will transmit the IMSI in the RADIUS attribute: Filter-Id (11). Default no. NOTE: The call number of the dial attempts must begin with the LAIN or the port number if CHADDR is not used. The following routing entry must be added:MapAll*??01:<LAIN>=<LAIN>*??01: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,0Example 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,1VoipStatLogging=<mode> When Yes is entered, statistic values (e.g. fraction lost, round trip time, etc.) for the VoIP profile are saved into the protocol.log file every ten minutes. This is helpful during problem analysis when IP issues occur (de-fault = No).Table 5.22 route.cfg: VoIP Management Parameters (continued)VoIP Management Parameters
CONFIGURATION FILESCHAPTER 591iGATE 15.0. Revised: 2009.5.3.3 GATEKEEPER PROFILESGatekeeper profiles are used to connect the iGATE to several systems by using a gatekeeper if the protocol isH.323. It is possible to configure different gatekeepers for different destinations and to define backup gatekeepers.These gatekeeper profiles are then assigned to the VoIP profiles:Table 5.23 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>iGATE’s defined prefix(es). Use a space to separate entries.RasId=<name>The alias used for gatekeeper registration.GkId=<name>The gatekeeper’s alias.GkPwd=<name>Password to log onto the gatekeeper. If you do not use authentication, leave this entry blank.GkAdd=<ip addr>The gatekeeper’s IP address.GkTtl=<sec>Gatekeeper time to live (default 0 means infinite).GkMaxChan=<count>Max. number of channels used for this gatekeeper. If this parameter is not defined (default), there will be no limit.GkDynMaxChan=<mode>The static number of available channels in the gatekeeper profile (GkMaxChan=<count>) is replaced with a dynamic number of active mobile ports (up to the number entered in GkMaxChan) when Yes is entered here. Default is No.GkUseStun=<mode>Enter yes (default) to use the STUN values for the GK profile.
CONFIGURATION FILESCHAPTER 592iGATE 15.0. Revised: 2009.5.3.4 REGISTRAR PROFILESRegistrar profiles are used to register the iGATE with a SIP registrar. It is possible to configure different registrarsfor different destinations and to define backup registrars. These registrar profiles are then assigned to the VoIPprofiles:GkTerminalAliasWithPrefix=<mode>Some gatekeepers may require that prefixes are listed in the Terminal Alias section. Enter Yes to activate this function; default value is No). GkTerminalTypeWithPrefix=<mode>Enter no to deactivate sending the Dialed Prefix Information in the Registration Request (default yes).GkDynRai=<mode>When yes is entered, the GK receives an RAI (resource availability indication) when a status change occurs on the available mobile channels. When no is entered, the RAI is sent with each ARQ (admission request) and DRQ (disengaged request). Default is no.GkNoResourceAvailableIndication=<mode>With this parameter the <system> will not send RAI indications to the Gatekeeper. Default No.Table 5.24 route.cfg: Registrar Parameters Registrar Parameters[Registrar:<name>]The name of the registrar profile.RegId=<name or ip addr>Host name or IP address used in the register’s request header. Bear in mind that the DNS service must be active if you enter the host name.RegOwnId=<name@ip addr/domain>Typically a host name or telephone number followed by an @ sign and a domain name or IP address. The entry used in the From: field. The default setting is RegUser@RegId.RegSameCallID=<mode>When Yes is set (default), the same caller ID is always used for SIP registration. Set No to change the caller ID for each SIP registration.RegContact=<name or ip addr>Used in the Contact: field.Table 5.23 route.cfg: Gatekeeper Parameters (continued)Gatekeeper Parameters
CONFIGURATION FILESCHAPTER 593iGATE 15.0. Revised: 2009.RegContactParam=<string>Sets additional header-parameters in the contact field (e.g.the q-value: RegContactParam=q=1.0).RegUser=<name>Enter a username for authorization.RegPwd=<password>Enter a password for authorization.RegProxy=<ip addr>Enter an alternative IP address if you want the request to be sent to an address other than the one entered in RegId.RegExpires=<sec>Enter the number of seconds registration is to be valid. Default 0 means infinite.RegPing=<sec>Interval (in seconds) for the registrar ping. The iGATE sends an empty UDP packet to the registrar’s IP address. The packet is essentially an alive packet to avoid possible firewall problems.RegSignalling=<int>Determines the profile’s signaling protocol for registration with the SIP registrar. 1=SIP udp (default)2=SIP tcp3=SIP tlsRegUseReceived=<mode> Enter Yes when an iGATE appears behind a NAT and STUN cannot be used. Default No..RegSameCallID=<mode> The same call ID is used for SIP registration Enter No to change the call ID for every reregistration. (default Yes).Table 5.24 route.cfg: Registrar Parameters (continued)Registrar Parameters
CONFIGURATION FILESCHAPTER 594iGATE 15.0. Revised: 2009.5.3.5 RADIUS PROFILESRadius profiles are used to connect the iGATE to a Radius server. You can use a Radius server for different desti-nations and for access and/or accounting. These Radius profiles are then assigned to the VoIP profiles: Table 5.25 route.cfg: Radius Parameters Radius Parameters[Radius:<name>]The name of the Radius server profile assigned to one or more VoIP profiles.Host=<name or ip addr>Radius server’s host name or IP address. Bear in mind that the DNS service must be active if you enter the host name.User=<name>Enter a username for authorization.Password=<password>Enter a password for authorization.Secret=<secret>Enter the shared secret.OwnId=<name or ip addr>Host name or IP address used in the NAS identifier or NAS IP address (Cisco VSA gateway ID).ServiceType=<num>As defined in RFC 2865, Chapter 5.6.RequestTimeout=<sec>Number of seconds during which the request is repeated if the Radius server does not respond.RequestRetries=<count>Number of packet retries sent at one time.StopOnly=<mode>When yes is entered, only Accounting Request Messages with the status type stop are transmitted to the Radius server.AlwaysConnected=<mode>Enter No (default) to set the value for the field ConnectedTime to that of the field DisconnectedTime in accounting-stop messages when the call was not connected.
CONFIGURATION FILESCHAPTER 595iGATE 15.0. Revised: 2009.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.CallType=<int>Enter one of the following to define the call type:3 = VoIP and telephony2 = VoIP only1 = Telephony onlyFramedProtocol=<int>Enter one of the following to define the framed protocol (see RFC 2865, Chapter 5.7):1 = PPP2 = SLIP3 = AppleTalk Remote Access Protocol (ARAP)4 = Gandalf proprietary SingleLink/MultiLink protocol5 = Xylogics proprietary IPX/SLIP6 = X.75 SynchronousNasId=<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.25 route.cfg: Radius Parameters (continued)Radius Parameters
ROUTING EXAMPLESCHAPTER 696iGATE 15.0. Revised: 2009.6 ROUTING EXAMPLES6.1 IGATE INTEGRATION IN A CARRIER NETWORKIn the following example, a iGATE32 is inte-grated in a carrier network via DSS1. It is con-nected to a vGATE and receives SIM-cardinformation from a centralized SIM-card serv-er. The IP address for the vGATE Control Unitis 172.16.0.100. The parameter SIMS is usedin SIM<x> to connect the mobile controllerwith the vGATE. All calls coming from ISDN aresent to two different mobile networks: Callswith the prefixes 01555 and 01556 are sent tothe carrier with the LAIN 26212 at controllers0-15. Calls with the prefixes 01444 and 01445are sent to the carrier with the LAIN 26313(controllers 16-31). Digit collection is activat-ed, so that incoming calls with overlap dialing are not transmitted until the number is complete or a wait timer (5seconds) has run out. The NEXT parameter makes sure that calls are distributed evenly to the individual mobilechannels in the trunk group. The parameter CHADDR ensures that calls are not misrouted, since the controller def-inition changes to the SIM-card’s LAIN when a SIM card is mistakenly used for another mobile controller. Problemscan occur when SMS messages are also sent, as service center numbers are definitively configured. Configuration in the pabx.cfg Configuration in the route.cfgThe parameter VoipUseIpStack must be set in the VoIP profile.Subscriber00 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIMS,IMSI] CHADDR ALARM NEXTSubscriber01 = TRANSPARENT ROUTER GSM[0000,00000,+491555555,1,1,1,SIMS,IMSI] CHADDR ALARM ....Subscriber16 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIMS,IMSI] CHADDR ALARM NEXTSubscriber17 = TRANSPARENT ROUTER GSM[0000,00000,+491666666,1,1,1,SIMS,IMSI] CHADDR ALARM ....Subscriber32 = TRANSPARENT ROUTER ALARMSubscriber33 = TRANSPARENT ROUTER ALARMSimCtrlUnitAddress=172.16.0.100[System]DTMFWaitDial=5MapAll01555=|2621201555<<17MapAll01556=|2621201556<<17MapAll01444=|2621301444<<17MapAll01445=|2621301445<<17iiIPNetwork
ROUTING EXAMPLESCHAPTER 697iGATE 15.0. Revised: 2009.6.2 IGATE INTEGRATION WITH SIM-CARD SWITCHING IN AN H.323 CARRIER NETWORKIn the following example, a iGATE32 is inte-grated in a carrier network via H.323. The sys-tem contains six SIM cards for each mobilechannel, and the SIM 24 Carrier is used. Allcalls coming from VoIP are routed to the mo-bile network. Four VoIP Modules with 16 me-dia channels each are attached in the system.H.323 is used as the signaling protocol and agatekeeper is used in the VoIP network. Be-cause the gatekeeper assigns and authorizesthe peer, only one VoIP profile is necessary.Since the peers may use various compressionalgorithms, you can define several if you sochoose. The codec with the highest priority isG.729. If the peer does not support it, G.726 32Bit/sec, G.711a, G.711u are also possible. Silence suppression isactive. The gatekeeper’s IP address is 192.168.0.10. This gatekeeper profile can handle up to 30 simultaneousVoIP calls. This value is dynamic and changes depending on the number of active SIM cards. The iGATE’s alias isiGATE01. The prefix list is 01555 01556 01444 01445. The gatekeeper’s alias is GK1 and no password is used.Calls with the prefixes 01555 and 01556 are sent to the carrier with the LAIN 26212 at controllers 0-15. Calls withthe prefixes 01444 and 01445 are sent to the carrier with the LAIN 26313 (controllers 16-31). Digit collection isactivated, so that incoming calls with overlap dialing are not transmitted until the number is complete or a waittimer (5 seconds) has run out. The NEXT parameter makes sure that calls are distributed evenly to the individualmobile channels in the trunk group. The parameter CHADDR ensures that calls are not misrouted, since the con-troller definition changes to the SIM-card’s LAIN when a SIM card is mistakenly used for another mobile controller.Problems can occur when SMS messages are also sent, as service center numbers are definitively configured. Theparameter LIMIT is set so that the system automatically switches to the mobile controllers’ SIM cards when theactive SIM card has been used for 3600 seconds. The parameter CONTINUE makes sure the mobile channelswitches to the first SIM card after the limit has been reached on the last SIM card. The SIM card will not switchuntil currently active calls have been disconnected. Configuration in the pabx.cfg Subscriber00 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24,IMSI] CHADDR LIMIT[3600,3600,3600,3600,3600,3600] CONTINUE ALARM NEXTSubscriber01 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24,IMSI] CHADDR LIMIT[3600,3600,3600,3600,3600,3600] CONTINUE ALARM ....Subscriber34 = TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMSubscriber35 = TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMChargeUnitGenerate=1LimitWODisc=ONCarrierPSTN
ROUTING EXAMPLESCHAPTER 698iGATE 15.0. Revised: 2009.Configuration in the route.cfg[System]DTMFWaitDial=5MapAll01555=|2621201555<<17MapAll01556=|2621201556<<17MapAll01444=|2621301444<<17MapAll01445=|2621301445<<17[Voip:DF]VoipDirection=InVoipPeerAddress=10.0.0.0VoipIpMask=0xffff0000VoipSignalling=0VoipCompression=g729 g72632 g711a g711uVoipSilenceSuppression=YesVoipMaxChan=30VoipTxM=2VoipGk=GK1[Gatekeeper:GK1]RasPort=1719OwnRasPort=1719RasId=iGATE01RasPrefix=01555 01556 01444 01445GkId=GKGkAdd=192.168.0.10GkPwd=GkTtl=300GkMaxChan=30GkDynMaxChan=Yes
ROUTING EXAMPLESCHAPTER 699iGATE 15.0. Revised: 2009.6.3 IGATE AS A SECOND-GENERATION LCR WITH VOIPIn the following example of a PBX connection,all mobile calls are terminated through the mo-bile channels. Eight mobile channels form agroup for one mobile network. One SIM card isavailable on each mobile channel. Digit collec-tion is activated, so that incoming calls withoverlap dialing are not transmitted until thenumber is complete or a wait timer (5 seconds)has run out. The NEXT parameter makes surethat calls are distributed evenly to the individ-ual mobile channels in the trunk group. If all ofa carrier’s SIM cards are busy, rerouting(redirect3) via PSTN is automatically initi-ated. All international calls are terminated toVoIP (40). The system contains two VoIP Modules, for a total of 32 media channels. The VoIP carrier profile DFand the SIP protocol are used. National calls are routed through the carrier with the prefix 010xx. All other callsare 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. All incoming calls from the mobile networks are routed to the PBX’s central number(001). For the VoIP profile DF, the system uses the registrar reg and registers with user@sip-carrier.de,username user and password pwd. SIP UDP is used for signaling. A maximum of 30 media channels with theG.729 codec can be used. The Peer is sip-carrier.de.Configuration in the pabx.cfg Subscriber00 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4,IMSI] CHADDR ALARM NEXTSubscriber01 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4,IMSI] CHADDR ALARM ....Subscriber08 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4,IMSI] CHADDR ALARM NEXTSubscriber09 = TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4,IMSI] CHADDR ALARM ....Subscriber16 = TRANSPARENT ROUTER ALARMSubscriber17 = TRANSPARENT ROUTER ALARMSubscriber18 = TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMSubscriber19 = TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMLANIPNetworkPSTNISDNISDNEthernet
ROUTING EXAMPLESCHAPTER 6100iGATE 15.0. Revised: 2009.Configuration in the route.cfg[system]DTMFWaitDial=5Restrict9=10Restrict40=10Restrict26212=10001Restrict26213=10001MapOut01555=|2621201555<<17MapOut01556=|2621201556<<17MapOut01666=|2621301666<<17MapOut01665=|2621301665<<17MapOut00=40DF:00MapOut0=010xx0MapOut?=9?Redirect326212=ARedirect326213=AMapAllA=9[Voip:DF]VoipDirection=IOVoipPeerAddress=sip-carrier.deVoipIpMask=0xffffffffVoipSignalling=1VoipCompression=g729 t38VoipSilenceSuppression=YesVoipMaxChan=60VoipTxM=4VoipOwnAddress=user@sip-carrier.deVoipUser=userVoipPwd=pwdVoipRegistrar=reg[Registrar:reg]RegId=sip-carrier.deRegOwnId=user@sip-carrier.deRegContact=user@sip-carrier.deRegUser=userRegPwd=pwd
MOBILE CONFIGURATION OPTIONSCHAPTER 7101iGATE 15.0. Revised: 2009.7 MOBILE CONFIGURATION OPTIONS7.1 CONNECTION TO A VGATEThe vGATE is a system that enables more convenient management of a network of iGATE systems. All SIM cardsin the network are installed in and maintained at a central server, so that it is no longer necessary to install SIMcards into each gateway. The iGATEs connected to the vGATE do not require SIM-card carriers, as the vGATE con-tains SIM-card carriers for the entire network.The following parameters must be configured in the pabx.cfg of each iGATE connected to the vGATE. After theparameters have been entered, you must restart the iGATE to activate the changes: 7.2 MODULE DISTRIBUTION OF VARIOUS MOBILE NETWORKSYou can assign each mobile port in the iGATE system either one mobile network or different access groups to dif-ferent mobile networks. The port numbers in the iGATE must be the same for the individual groups. The keyword NEXT ensures equal distribution of calls. The following configuration samples (from the pabx.cfg configuration file) show the changes:Example 1 All ports in the following example must have the same number for all mobile channels to routecalls to the same mobile network. The subscriber line of the first port must also contain thekeyword NEXT to ensure the equal distribution of calls.Be sure to save a backup copy of the configuration files before making changes. Changing configuration data and/or SIM-card positions may lead to malfunctions and/or misrouting, as well as possible consequential damages. Make changes at your own risk. TELES is not liable for any damages resulting from or related to such chang-es. Therefore, please thoroughly check any configuration changes you or a third party have made.Bear in mind that no SIM-card carriers are to be inserted in iGATEs connected to a vGATE.SIMSEnter this keyword in the Subscriber lines of the mobile controllers to connect the system to a vGATE.EXAMPLE: Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIMS] CHADDR ALARMSimCtrlUnitAddress=<ip addr>Enter the vGATE Control Unit’s IP address. Set this parameter in the IP configuration section.EXAMPLE:SimCtrlUnitAddress=192.168.0.1!!ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7102iGATE 15.0. Revised: 2009.Example 2 In the following example, a group of 16 mobile channels is assigned to three different mobilenetworks. The subscriber line of the first port in each group must contain the keyword NEXTto ensure the equal distribution of calls....Controller00=20 GSMController01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSMController05=20 GSMController06=20 GSMController07=20 GSMController08=20 GSMController09=20 GSMController10=20 GSMController11=20 GSMController12=20 GSMController13=20 GSMController14=20 GSMController15=20 GSM...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM NEXTSubscriber01=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber02=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber03=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber04=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber06=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber07=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber08=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber09=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber11=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber12=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM...
MOBILE CONFIGURATION OPTIONSCHAPTER 7103iGATE 15.0. Revised: 2009.7.3 NETWORK-SPECIFIC MOBILE ROUTING7.3.1 USING A FIXED MOBILE PORT ADDRESSThe customer’s network routes calls to the mobile network with a defined prefix. Because this code is not alwaysuniform, the iGATE might have to convert it. Conversion requires the following information:The mobile network’s access numberDestination number format (with or without prefixes, national or international)Conversion occurs according to the following formula:converted as:Be sure to make the following entry in the route.cfg configuration file to configure this conversion:The iGATE system converts national into one zero and international into two zeros....Controller00=20 GSMController01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSMController05=20 GSMController06=22 GSMController07=22 GSMController08=22 GSMController09=22 GSMController10=22 GSMController11=22 GSMController12=24 GSMController13=24 GSMController14=24 GSMController15=24 GSM...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM NEXTSubscriber01=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber02=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber03=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber04=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber06=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM NEXTSubscriber07=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber08=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber09=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber11=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber12=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM NEXTSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] ALARM...<national/international><prefix[incoming]>=<destination number><port><mobile network access number><destination number>MapAll<nat./int.>prefix[incoming]>=<port><mobile network access number>
MOBILE CONFIGURATION OPTIONSCHAPTER 7104iGATE 15.0. Revised: 2009.The following configuration exemplifies this conversion as it might occur in Germany:This example shows how the customer’s network provides the prefix international+49+1555+destination numberfor one mobile network, and international+49+1556 for the other. The configuration entries see to it that00491555+destination number is converted to 2001555+destination number and 00491556+destination num-ber is converted to 2101556+destination number. The calls to the carrier with prefix 01555 are routed to portswith the number 20 and calls to the carrier with prefix 01556 are routed to the ports with the number 21.7.3.2 USING THE LAIN AS THE MOBILE PORT ADDRESSUse the LAIN as controller with the CHADDR parameter to prevent logging onto the wrong SIM card. This will en-sure that routing is network specific. The following example is based on the German country code. One carrier’sLAIN is 26212 and the other carrier’s LAIN is 26213:pabx.cfg...MapAll00491555=2001555MapAll00491556=2101556......Controller00=20 GSMController01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSMController05=20 GSMController06=20 GSMController07=20 GSM...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber01=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber02=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber03=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber04=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber06=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber07=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARM...If you remove the keyword CHADDR from the pabx.cfg, you must restart the system. Controllers belonging to the same trunk group must have the same address. You must delete all routing entries based on port addresses when using the LAIN as con-troller.ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7105iGATE 15.0. Revised: 2009.route.cfg7.3.3 FIXED LAIN FOR A MOBILE PORTEnter CHADDR[<addr>] to remove a mobile controller belonging to an LAIN group from the standard routingprocess (e.g. for specific routes or only for SMS transmission). The port address can be set to <addr>.Example:7.4 INCOMING VOICE CALLS FROM MOBILEIncoming mobile calls (service indicator 01 represents voice calls) can be routed to a specified number. This enableseach mobile controller to receive a unique identifier. It will then be mapped to a number: The mobile controllers can also have the same identifier, so that all voice calls (service indicator 01) from controller20 are sent to number 1111 at port 9. This number could, for example, serve a call center.7.5 BLOCKING PORTSThis function allows you to block a port, so that the corresponding mobile channel is omitted from the distributionof calls. The function is particularly useful when mobile channels fail or SIM cards cannot be immediately replaced. To block a port (i.e. a mobile channel), enter the keyword CHINC[...] in the Subscriber line.In Example 1 >, port 10 is blocked. Example 1To activate the port, remove the entry and enter Activate configuration.It is also possible to block an entire port with the remote administration program GATE Manager. The CHINC[...]function is not necessary with this application. The port’s status is displayed by remote administration. You canremove the block with Activate a configuration or with the Unblock option....MapAll01555=2621201555...MapAll01556=2621301556...Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR[444] ALARMMapAllSMS=444 DATARestrict20=90123 01Restrict21=91234 01Restrict20=91111 01...Subscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM4] CHADDR ALARM CHINC[01,01]...
MOBILE CONFIGURATION OPTIONSCHAPTER 7106iGATE 15.0. Revised: 2009.7.6 SETTING LIMITSThis function enables you to monitor time units. A unit can be set, either to the defined time interval or in 10-secondintervals (default value). At the beginning of the defined unit, the current connection is torn down either immedi-ately or when the call has been terminated (cf. Chapter 7.7.3 on page 108 >); no more connections will be setup. An alarm also goes off and an entry is generated in the log file. Setting SIM Time LimitsIn the following example, the mobile channel shuts down at the beginning of the last 10-second unit of 6,001: Setting the Default Time WindowIn the following example, the mobile channel shuts down when a calculated number of units set in LIMIT has com-menced. If ChargeUnitGenerate=<sec> is configured, the mobile channel will shut down at the beginning of thelast unit entered in LIMIT multiplied by the value entered here. The default value for this parameter is 10 seconds.Bear in mind that the value entered in LIMIT may not exceed 65535. In the example, the mobile channel will shutdown at 60,000 seconds. Setting Start UnitsThe following example shows how you can use the keyword ChargeUnitFirst=<seconds> to configure a startingunit for LIMIT. The following entries are used for SIM card rates where the first defined number of seconds arealways charged (e.g. the first minute). After this initial number of seconds has passed, the subsequent charges willbe calculated in intervals defined by ChargeUnitGenerate (e.g. every 10 seconds): Information about the active SIM cards can be found in GATE Manager and Port Status. Bear in mind that you must add 1 to the values you wish to set, since the units change at the beginning of each interval....Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4] CHADDR ALARM NEXT LIMIT[6001,-]......ChargeUnitGenerate=1...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4] CHADDR ALARM NEXT LIMIT[60001,-]......ChargeUnitFirst=60ChargeUnitGenerate=10...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4] LIMIT[6061,-] ALARM NEXT......ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7107iGATE 15.0. Revised: 2009.To remove limits from the configuration, follow these steps:Enter LIMIT[-].Activate the configuration.Delete the entry LIMIT[-].Activate the configuration again.7.7 AUTOMATIC SIM SWITCHINGThis function enables you to monitor time quotas. A limit can be set, either to the defined time interval or in 10-second intervals (default value). When this value is reached, the current connection is torn down either immediatelyor when the call has been terminated; either no more connections will be set up or the system will switch to anotherSIM card. An alarm also goes off and an entry is generated in the log file. You can configure different limits for each SIM card per mobile channel. To activate this function, enter the keywordLIMIT[<val1>,<val2>,<val3>,<val4>,<val5>,<val6>] at subscriber for the corresponding port. <valx> defines anumber of units as a threshold value for the respective SIM card. If only one limit is entered, this limit will apply forall SIM cards at this port. If a dash ( - ) is entered for <valx>, no limit will apply for the corresponding SIM card. If only two values are entered,a dash must be entered for the other SIM cards; these SIMs will have no limit. A corresponding alarm message isgenerated when the limit on each card has been reached. If the keyword CHANGE is configured, the mobile chan-nel will not switch beyond the sixth SIM card. Different settings are possible for the various SIM-card carriers. The number entered (4, 24) refers to the numberof slots. The respective number of SIMs per mobile channel is 1 or 6.The following configurations are possible. Settings shown here are for the SIM-24 carrier:Make sure the SIM24 card carrier is inserted and the size of the SIM-card carrier (SIM24) is entered in the Subscriber line.Table 7.1 SIM Switching ConfigurationsConfiguration DefinitionLIMIT[10,20,30,40,10,20] CHANGEEach SIM card has a defined limit. LIMIT[10,10,10,10,10,10] CHANGEEach SIM has the same limit.LIMIT[10,-,-,-,-,-] CHANGE The first SIM has a defined limit, the second has none.LIMIT[10,20,0,0,10,20] CHANGE SIMs 1, 2, 5 and 6 have defined limits. The SIMs in positions 3 and 4 are not used.ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7108iGATE 15.0. Revised: 2009.If the keyword CONTINUE is configured, the mobile channel will switch beyond the sixth SIM card. When the limiton the last card has been reached, the mobile channel will switch back to the first card.7.7.1 SWITCHING SIMSIn the following example, the mobile channel shuts down and switches to the next SIM card when 6,000 intervalsof 10 seconds each have passed. The port is blocked after the limit has been reached on the last SIM card:7.7.2 CYCLICAL SIM SWITCHINGIn the following example, the mobile channel shuts down and switches to the next SIM card when 6,000 intervalsof 10 seconds each have passed. The mobile channel switches to the first SIM card after the limit has been reachedon the last SIM card. To reset the counter on a monthly basis, see Chapter 11.4.1 on page 219 >: In the following example, only two SIM cards are inserted in the SIM-card carrier. These SIMs are used alternatelyin intervals of 3600 seconds each: 7.7.3 IMMEDIATE SIM SWITCHINGIn the following example, the mobile channel shuts down after the call has been disconnected, and switches to thenext SIM card when 6,000 intervals of 10 seconds each have passed. When the parameter LimitWODisc is ON, thecall will be torn down when the calling party hangs up. If it is set at OFF, the call will be terminated immediatelywhen the limit is reached: ...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000,6000,6000,6000,6000,6000] CHANGE...Bear in mind that resetting the counters results in termination of in cyclical SIM switching and is to be avoided when cyclical SIM switching is used....Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000,6000,6000,6000,6000,6000] CONTINUE......ChargeUnitGenerate=1Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXTLIMIT[3600,3600,0,0,0,0] CONTINUE...LimitWODisc=OFF...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000,6000,6000,6000,6000,6000] CHANGE......ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7109iGATE 15.0. Revised: 2009.7.7.4 COUNT STATUS INFORMATIONTo find information about the current counts and limits for each mobile channel, click Statistics in theGATE Manager.For mobile ports:Count A-F For each mobile channel. Counts are the time slices (from 0 to the limit value) for the individualSIM cards (1-6). When a SIM’s set time limit is reached, the channel will disconnect and the next SIM willlog on. Click Reset/Set Counters in the Statistics context menu in GATE Manager to reset the counters (defaultvalue is 0). You can also configure the counters to reset automatically (cf. Chapter 11.4.1 onpage 219 >).7.8 DEFINING TIME LIMITS FOR CALLSBy entering the parameter CALL in the Subscriber line, you can terminate calls that reach a defined time limit. Foreach call the limit is reset at 0. You can define a value anywhere within <limit>-<random>, and you can define amaximum value for <random>. The value entered for CALL must be at least 30 seconds. If this parameter is configured once, it will be set in each configuration file. If you prefer not to use it for all SIMs,set the limit higher than any call is likely to last (e.g. 360,000 seconds). To deactivate this function, remove theentry from the pabx.cfg and restart the system.Example:The following entry is required if the iGATE is used in conjunction with a vGATE:Resetting the counters results in termination of in cyclical SIM switching and is to be avoided when cyclical SIM switching is used.If LIMIT is configured, SIM 1 must be configured in the pabx.cfg for the corre-sponding mobile port.Bear in mind that you must add 1 to the values you wish to set, since the units change at the beginning of each interval.ChargeUnitGenerate=1;defines the factor for the limit entry (600*1=600sec)ChargeUnitDivisor=5 ;random value that defines the maximum call duration between 595 and 600secs...Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIM24] CALL[601]Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIMS] CALL[600]iiii
MOBILE CONFIGURATION OPTIONSCHAPTER 7110iGATE 15.0. Revised: 2009.7.9 PAUSE BETWEEN TWO CALLSIf the parameter WAIT appears in the Subscriber line, the mobile controller will not be used after a successful con-nection or A-side release for a random amount of time between 1 and 30 seconds (default). To set another randominterval, enter the lower and upper values between 0 and 255 in square brackets after the parameter.Example:If the parameter WAITBREJ appears in the Subscriber line, the mobile controller will not be used after B-side release(GSM network) for a random amount of time between 1 and 30 seconds (default). To set another random interval,enter the lower and upper values between 0 and 255 in square brackets after the parameter. Example:7.10 TIME-CONTROLLED SIM SWITCHINGYou can define a time at which a mobile channel will change to another SIM card (up to six SIM cards are possiblefor this option). Before proceeding, please refer to Chapter 5.2.1.3 > for basic information.You must define all time windows you would like to use in the [System] section of the pabx.cfg, in the subsectionnight configuration.The following entry in the configuration file pabx.cfg is necessary: Night<num>=<time> <day> Example: In the following example, six time windows are defined. The standard configuration is active ev-ery day from 12:00 midnight to 4:00 a.m.. The time window Night1 is active from 4:00 to 8:00This function cannot be used in conjunction with the LIMIT function described in Chapter 7.7 >. Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24,IMSI] CHADDR WAIT[20,40] ALARMThe parameter WAITBREJ works only if the parameter WAIT has also been set. Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24,IMSI] CHADDR WAIT[20,40] WAITBREJ[20,40] ALARM iiii
MOBILE CONFIGURATION OPTIONSCHAPTER 7111iGATE 15.0. Revised: 2009.a.m., etc.To generate a NightConfiguration section for SIM switching, copy the complete Subscriber subsection from the[System] section after making the appropriate entries in the [Nightx] section.Finally, enter the SIM-card number (1-6 for the SIM 24 Carrier) that is to be active during the specified time periodin the mobile port’s subscriber entry.Example: In the following example, SIM cards change in the individual time windows (as configuredabove). Only the Subscriber lines for controllers 12-15 are presented in simplified form. In aproper configuration, all Subscriber lines must be defined. The only difference is in the active SIM card. Activate the configuration after the required files have been copiedonto the system.;Night configuration; ---------------------Night1=04:00 11111111Night2=08:00 11111111Night3=12:00 11111111Night4=16:00 11111111Night5=20:00 11111111NightResetTime=00:00 11111111[System]...Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM24] ALARM... [Night1] ... Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,2,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,2,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,2,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,2,1,1,SIM24] ALARM... [Night2] ... Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,3,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,3,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,3,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,3,1,1,SIM24] ALARM... [Night3] ... Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,4,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,4,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,4,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,4,1,1,SIM24] ALARM... [Night4] ... Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,5,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,5,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,5,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,5,1,1,SIM24] ALARM... [Night5] ... Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,+49555,6,1,1,SIM24] ALARMSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,+49555,6,1,1,SIM24] ALARMSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,+49555,6,1,1,SIM24] ALARMSubscriber15=TRANSPARENT ROUTER GSM[0000,00000,+49555,6,1,1,SIM24] ALARM...
MOBILE CONFIGURATION OPTIONSCHAPTER 7112iGATE 15.0. Revised: 2009.Bear in mind, that you must also make the appropriate entries in the corresponding route.cfg sections. For moreinformation, please refer to Chapter 5.3 >.Time-Controlled Logoff of a Mobile Channel or SIM CardIf a dash (-) is entered in the SIM-card position, the SIM card will log off automatically. Time-controlled activationof configuration files makes it possible to shut off unneeded SIMs, for example at night. Example:7.11 MOBILE-USER PBX CALLBACKWhen the iGATE is implemented in a corporate network and connected to a PBX or between a PBX and the outsideline, the following configuration entry activates a feature, that uses a mobile caller’s OAD to connect with the lastPBX extension the caller unsuccessfully dialed:DialBack=<hours>The callback list is active for the number of hours entered. Example: In the following example, the callback list is active for the previous five hours. The German coun-try code is used for the LAINs. All calls with the prefixes 1111 and 2222 are terminated throughthe carrier with the LAIN 26212. Calls with the prefix 3333 are terminated through the carrierwith the LAIN 26213: This function cannot be used in conjunction with the LIMIT function described in Chapter 7.7 >.[System]Subscriber12=ALARM GSM[0000,00000,+49555,1,1,1,SIM24]Subscriber13=ALARM GSM[0000,00000,+49555,1,1,1,SIM24]Subscriber14=ALARM GSM[0000,00000,+49555,1,1,1,SIM24]Subscriber15=ALARM GSM[0000,00000,+49555,1,1,1,SIM24][Night1]Subscriber12=ALARM GSM[0000,00000,+49555,2,1,1,SIM24]Subscriber13=ALARM GSM[0000,00000,+49555,2,1,1,SIM24]Subscriber14=ALARM GSM[0000,00000,+49555,2,1,1,SIM24]Subscriber15=ALARM GSM[0000,00000,+49555,2,1,1,SIM24][Night2]Subscriber12=ALARM GSM[0000,00000,+49555,-,1,1,SIM24]Subscriber13=ALARM GSM[0000,00000,+49555,-,1,1,SIM24]Subscriber14=ALARM GSM[0000,00000,+49555,-,1,1,SIM24]Subscriber15=ALARM GSM[0000,00000,+49555,-,1,1,SIM24]Callback is not possible for VoIP calls.DialBack=5MapAll1111=262121111MapAll2222=262122222MapAll3333=262133333iiii
MOBILE CONFIGURATION OPTIONSCHAPTER 7113iGATE 15.0. Revised: 2009.7.12 OPTIONAL MOBILE QUALITY PARAMETERSThe following parameters can be set for specific carriers if SIM cards for different mobile networks are used anddifferent configurations must be set.For all controllers without an LAIN, the following default setting applies: GSM=Up to four additional carrier-specific entries may be set:GSM1=<Lain1> ALFI[<val1/val0>]...GSM2=<Lain2> ...GSM3=<Lain3> ...GSM4=<Lain4> ...Up to four LAIN-specific configurations are possible. The user must enter the index (1 to 4). The LAIN appears asthe first entry behind the equal sign. Everything else follows.Make sure that no Restrict entries are configured for these mobile controllers.There is no automatic default behavior for this feature! All options must always be entered. We recommend that you enter GSM= settings, as all controllers without a LAIN or with a default address use these options!iiii
MOBILE CONFIGURATION OPTIONSCHAPTER 7114iGATE 15.0. Revised: 2009.The following table describes specific signaling and quality parameters for configuration of the mobile interface. Table 7.2 Optional Mobile Parameters GSM=...Enter any of the following parameters after the equal sign for the following functions. Entries may appear in any order, but all entries must appear in the same line and in double-digit notation as follows:GSM=RSSI[10] STOP[18,08] ANNOUNCE[00,08] FAX[a2] ASR[20,35]ALERT[<sec>] Set this parameter to generate alert signal in the D channel immediately after dial-end signal. If you enter optional square brackets containing a number of seconds, the alert signal will occur when the number entered has passed.ANNOUNCE Set this parameter to define what happens when a recorded announcement is recog-nized:No ANNOUNCE entry (default)A D-channel PROGRESS message stating Inband Information Available will be generatedANNOUNCE[<cause>]The connection will be rejected with the defined ISDN cause value. Do not enter the cause value ff!ANNOUNCE[00,<sec>]A timeout for voice recognition is defined in seconds (default value: 120 seconds). After the interval entered has passed, the connection is torn down.ANNOUNCE[ff]The call will be connected as soon as an announcement is recognized.FORWARD[<cause>] For GE864-QUAD modules onlyThe connection will be rejected with the defined ISDN cause value when call forward-ing is detected.NOTE: The GSM network must support this feature for it to work.ASAL Announcement Stop during ALert: Set this parameter to release calls if the GSM net-work sends an alert message, after which voice is detected (e.g. the B-party rejects the call, which is then forwarded to the B-party’s voicemail following the ring state).The parameter ANNOUNCE[<cause>] must be set to activate this parameter.MINV[<count>] Minimum Voice detections: Parameter used with ASAL to define the number of voice detections in a row before the call is released (e.g. GSM-network background noise detected as voice). The default value is 1, but 2 is recommended.The parameters ANNOUNCE[<cause>] and ASAL must be set to activate this param-eter.ASR[<limit>,<calls>]Allows you to change the default value (40 calls at 30% ASR). For a definition of ASR, see Chapter 11.4.1 >.
MOBILE CONFIGURATION OPTIONSCHAPTER 7115iGATE 15.0. Revised: 2009.CDC[<seconds>,<count>]Call duration check. When more than (<count>) connected calls in a row occur with a call duration lower than <seconds>, an alarm is generated and the port is restart-ed.FAX[<cause>] This entry allows you to reject fax calls with the defined cause value.RSSI[<limit>] Configure this parameter to set a limit for the reception field strength. When the re-ception field strength falls below this limit, the mobile channel will be blocked. If the field strength is above the limit, the mobile channel will log on with the mobile carrier again. The values used are 0 to 31, which represent the following field strengths: -113dBm to -51 dBm. An error is generated in the protocol log. The result must be divided by 2.EXAMPLE: To define a field strength of -95 dBm, subtract -95 from-113 and divide the result by 2:- 113dB - (-95dB) = -18dB / 2 = 9Enter RSSI[9]STOP[<val1>,<val2>]This entry allows you to define a maximum number of connection setups that always result in a recorded message (<val1>) without an alert detection or call-connected signal. The second value (<val2>) counts calls that connect immediately without an Alert detection. The mobile port is blocked when the defined value is reached and an entry is recorded in the log file (...Err: Voice). In this way inactive SIM cards that are forwarded to a recording (with or without a connect from the mobile carrier) can be recognized and blocked so that they are removed from the routing process. The de-fault status of this function is off.NOCP When this option is configured and the call is from ISDN to GSM, the Call Proceeding signaling message will be eliminated from signaling. This may be necessary if the ISDN peer does not support Call Proceeding. Bear in mind that the peer’s Setup Ack Timer is usually set at 5 seconds, which means that an Alert must be generated as follows: GSM=ALERT[5]FMIN[xxx] FMAX[yyy] Sets the frequency range for ringtone recognition (default 400-444 Hz).EXAMPLE:GSM=FMIN[400] FMAX[444]ALFI[<val1/val0>] GSM module GE864-QUAD only. Switches the digital filter on (val=1) the Telit module to suppress frequencies below 250 Hz per LAIN during alerting. (switch off val=0)Please use the parameter to enable alert-tone detection for dual tone LAINs only (cf. Chapter 7.12 on page 113 >)Table 7.2 Optional Mobile Parameters (continued)GSM=...
MOBILE CONFIGURATION OPTIONSCHAPTER 7116iGATE 15.0. Revised: 2009.7.13 DEACTIVATING MOBILE REROUTING The following entries in the pabx.cfg enable you to deactivate rerouting for rejected calls: VOICE[<sec>] The voice channel in the switching matrix is connected after <sec> (default immedi-ately). The voice channel is activated no later than the point at which the call is con-nected.WND9 Voice recognition is activated in the GSM module if the GSM network signals WND9 (voice). If this parameter is not set, voice recognition is activated immediately when the GSM call is initialized.Module Q24xx only.WND2A Generates Alert when WIND:2 is received. Module Q24xx only.WND2N Suppresses voice detection after WIND:2 is received. Module Q24xx only.MINA[<count>] Defines the number of alert tones that are required before an Alert is recognized.AllClassNext=<mode>Enter AllClassNext=Off to deactivate rerouting for all rejected calls, regardless of the cause value (default not configured).NOTE: You cannot configure both AllClassNext and Class2Next simultaneously!Class2Next=offEnter Class2Next=Off to deactivate rerouting for calls rejected with a class 2 cause value (default not con-figured).NOTE: You cannot configure both AllClassNext and Class2Next simultaneously!SelfNext=<int>Set this parameter to reroute a failed call through the same port. <int> defines the number of call attempts. Recommended values for <int> are 2 or 3. Bear in mind that this parameter must be used in conjunction with the parameter AllClassNext=Off. Default not configured.EXAMPLE: SelfNext=3AllClassesNext=OffTable 7.2 Optional Mobile Parameters (continued)GSM=...
MOBILE CONFIGURATION OPTIONSCHAPTER 7117iGATE 15.0. Revised: 2009.7.14 DISCONNECTING CALLS AFTER RINGWhen the following parameter is configured, the call will be disconnected once the number of configured secondshave passed after the mobile network has sent the first ring:AWSTime=<sec>7.15 CHECKING PORTS/MOBILE CHANNELSMonitoring ASR for Mobile PortsASR monitoring of the last 40 calls occurs for all mobile ports. If the ASR (ASR2) is lower than 30 percent, an alarmis generated at the corresponding port and the port is blocked. The port is then restarted and a corresponding entryappears in the protocol.log file (ASR). The port is then unblocked.The following entry in the pabx.cfg causes the mobile port to block automatically when this error occurs three timesin a row:ASRBlock=OnWhen ASRBlock=Off is used, the port will be restarted and will remain open.The following parameter in the pabx.cfg file allows you to change the default value (30% for 40 calls): GSM=ASR[<percent>,<number of calls>]7.16 RECHARGING PREPAID SIMSPrepaid SIM cards are an alternative to mobile telephone SIMs with a contract. Instead of being billed retroactively,prepaid SIMs are paid for in advance and then recharged when they run out.The advantages of prepaid SIMs are:No monthly basic feeCost controlNo surprises resulting from unexpectedly high mobile telephone billsWhen the account is empty, it can be recharged. The recharging methods for prepaid SIM cards of different carriersvary:Recharging via SMS/USSDRecharging via call to a defined numberRecharging via DTMFAutomatic recharging via direct debitGSM=ASR[20,35]
MOBILE CONFIGURATION OPTIONSCHAPTER 7118iGATE 15.0. Revised: 2009.When prepaid SIMs that do not recharge automatically (e.g. through a credit card) are used in a iGATE, it is possibleto recharge them directly from the system. The following requirements apply:The SIM is registered and no connection is active. Exact knowledge of the mobile carrier-specific recharging procedure exists. One valid prepaid voucher exists for one recharge. iGATEs support of the following procedures:USSD message to the mobile carrier's account managerThe GATE Manager sends the configured USSD message through the iGATE to the account manager. USSDrecharging is the recommended and most reliable procedure, as it consists of a digital message.Unfortunately, only a few mobile carriers currently support USSD recharging. Please ask your mobile carrierif he supports USSD recharging.SMS message to the mobile carrier's account managerThe GATE Manager sends the configured SMS containing the voucher number through the iGATE to theaccount manager. Unfortunately, only a few mobile carriers currently support SMS recharging. Please askyour mobile carrier if he supports SMS recharging.Connection setup to the account manager with subsequent menu selection and DTMF-tone transmissionof the voucher number– Direct recharging: Connection setup from a telephone through the iGATE to the account manager andmanual DTMF-tone transmission.– Indirect recharging using the GATE Manager: The GATE Manager sets up a connections through theiGATE to the account manager and sends the configured DTMF tones automatically.7.16.1 RECHARGE PREPARATION7.16.1.1 CHECKING THE ACTIVE SIMTo avoid recharging the wrong SIM card, be sure to check the mobile controller's active SIM using theGATE Manager: Transmission errors, truncated connections, incorrect or altered recharging proce-dures can prevent successful recharging. Please bear in mind that 3 incorrect re-charge attempts (per SIM) can result in blocked SIMs. Recharge SIMs at your own risk. TELES is not liable for any possible loss.Direct recharging is the simplest procedure. Since a direct connection exists, it is pos-sible to react to commands and error messages immediately. Indirect recharging by means of USSD is the most reliable and quickest way to recharge SIMs if the config-uration in the TELES.GATE Manager and iGATE is correct.!!ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7119iGATE 15.0. Revised: 2009.GATE ManagerFigure 7.1 GATE Manager Port StatusConnect to the system and go to the Port Status window. The active position in the SIM-card carrier is displayedin the SIM # column. The mobile controller's active SIM is displayed in the IMSI column.7.16.1.2 ADDRESSING SIMS USING PORT- AND CONTROLLER-SPECIFIC ROUTINGSIM recharging for a specific mobile controller requires configuration and activation of port- and controller-specificrouting entries in the route.cfg or pabx.cfg configuration file. Usually SIM cards are assigned to a carrier's trunkgroup and all calls through the carrier's network are evenly divided between the mobile controllers in the group.This would also apply to recharge calls.The routing entry defined here sets up a connection to the network:MapAll<in>=<port>*<ctrl>01:<num>When the number <in> is dialed, a connection to <num> is set up through <port>*<ctrl>01: You can now man-ually enter DTMF tones using a telephone.To recharge all SIMs in the iGATE, configure the following mapping, whereby 4400 is an example for a numberthat matches the first controller and 12345 is the number for the account manager: 7.16.1.3 BLOCKING THE PORT CONTAINING THE RECHARGING SIMIf a call is active on the mobile port containing the SIM to be recharged, the recharging process will not occur. Forthis reason it is better to block the port before recharging the SIM. In the Connections window, you must checkthe status No Connection on the mobile port. Block Port does not tear down a connection, it only prevents a newconnection from being set up.MapAll4400=20*0001:12345 MapAll4401=20*0101:12345 MapAll4402=20*0201:12345 MapAll4403=20*0301:12345 MapAll4404=20*0401:12345 MapAll4405=20*0501:12345 MapAll4406=20*0601:12345 .......MapAll4431=20*3101:12345
MOBILE CONFIGURATION OPTIONSCHAPTER 7120iGATE 15.0. Revised: 2009.7.16.2 RECHARGING PROCEDURE7.16.2.1 DIRECT RECHARGING VIA CALLThis is the easiest method when it is possible to set up a telephone connection to the iGATE system via PSTN orVoIP. This call can be connected with the carrier's account manager over a defined mobile controller. This meansthe call is set up over the controller's active SIM. Then you simply follow the account manager's recharge instruc-tions. After the SIM has been successfully recharged, it can be used again for a certain amount of time.The call can be set up using a number of methods. This is also possible if there are not enough available telephonenumbers to handle all of the system's available mobile controllers.DLA via DTMFThe user calls a defined number in the system. The called number is connected with the DTMF platform.The digits that are transmitted via DTMF match those in the routing entries. When the connection to theaccount manager has been established, both legs will be connected (see Chapter 7.16.1.2 >).GATE Manager (described in Chapter 7.16.2.2 > below)That means no BRI connection is necessary for a telephone that is connected directly to the system!7.16.2.2 INDIRECT RECHARGING VIA GATE MANAGERThis chapter describes automatic recharging of prepaid SIMs using the GATE Manager. It is not necessary to set upa telephone connection to the iGATE. The GATE Manager can set up its own connection to the carrier's accountmanager and send the pattern of DTMF tones or a USSD message.Recharging via Call and Transmission of Preconfigured DTMF TonesThis procedure requires exact knowledge of the when and what information the mobile carrier requests. The cor-responding pauses following the connect, for menu selection, between the DTMF tones, for correct repetition ofthe DTMF tones must be correctly configured in the GATE Manager before the call is set up. This DTMF-tone pattern can be established by testing the recharging process on a mobile phone or by followingthe directions in Chapter 2.1 and noting the pauses and transmitted digits.After a connection has been set up between the iGATE and the GATE Manager, select Commands | Send Call.The window must contain either General, Version or Directory.Send Call opens a dialog to initiate calls or recharge SIMs.To recharge SIMs, the 1st Number (e.g. 12345) is the mapping to the prepaid platform through a defined con-troller (e.g. MapAll12345=20*0101:12345).Port- and controller-specific routing has a higher priority than the Block Port com-mand. This ensures that normal calls are blocked, but recharge calls can be sent through the defined mobile port.ii
MOBILE CONFIGURATION OPTIONSCHAPTER 7121iGATE 15.0. Revised: 2009.Optional: You can set up a second connection to hear the announcement from the prepaid platform if you enteryour own number into the box 2nd Number. Both connections will be torn down when the second number dis-connects. If no number is entered in this box, the call will disconnect when the last DTMF tone has been transmittedor when the last pause interval has passed. Activate the checkbox Advanced to open the DTMF boxEnter a series of DTMF tones in the DTMF box. Enter a p for a pause of 1 second and a P for a pause of 10 seconds.Example: The number for the prepaid platform's account manager is 12345. The telephone number to lis-ten along to the accounting procedure is 5554321, set up through controller 9 (no special rout-ing configuration is defined in the configuration files). Leave this dialog box empty if theaccounting process is not to be monitored.The voucher key is: 55555555555 (a short pause can also be defined between individual digits:for example, 5p5p5p5p5p5p5p5p5p5p5).To get to the voucher key query, the following pattern must be transmitted: P2ppppp1ppp. Fol-lowing transmission of the voucher key and a 10-second pause, the call will be torn down.Recharging via USSD Code (Unstructured Supplementary Services Data)Recharging prepaid SIMs using the GATE Manager and USSD is the most convenient solution if the prepaid carrieroffers this service. The USSD messages contains the prepaid voucher number.Configure an additional controller in the last position for DTMF functionality as follows:Example:Bear in mind that DTMF tones are only generated with connections into the mobile network. Test calls over the PRI, BRI or VoIP interfaces do not transmit DTMF tones and no tones can be heard!Controller36=41DTMFFigure 7.2 Recharging with DTMF Tonesii
MOBILE CONFIGURATION OPTIONSCHAPTER 7122iGATE 15.0. Revised: 2009.The corresponding Subscriber line will look like this:The configuration file route.cfg must contain the following entry in the [System] section:MapAllDTMF=<dtmf port>DTMFMapAll<place>??=<port>*??01:orMapAll<place>??=<LAIN>*??01:First a placeholder is defined, followed by ?? so that one mapping entry applies for the entire group of the carrier'smobile controllers. The right side of the mapping entry begins with the mobile port number or the port's LAIN.Example: In the following example, prepaid SIMs from 2 different carriers are used in the system. The lettersY and Z are used as placeholders, and the carrier's LAINs are 26212 and 26213 (based on theGerman country code):Subscriber36=TRANSPARENT ROUTER CHMAX[5]MapAllDTMF=41DTMFMapAllY??=26212*??01:MapAllZ??=26213*??01:
MOBILE CONFIGURATION OPTIONSCHAPTER 7123iGATE 15.0. Revised: 2009.Set up a connection to the system through the GATE Manager and select Commands | Send Call. Enter DTMFin the 1st Number dialog box. In the 2nd Number dialog box, enter the carrier's placeholder (Y or Z) and thenumber of the controller in which the SIM card is active (15 or 05). Enter a 0 in front of single-digit controller num-bers. Then enter the carrier's USSD code (*101*) and the voucher number (44444444444 or 55555555555). TheUSSD command ends with #.Configuration entries for recharging confirmation are described in Chapter 3.Recharging via SMS (Short Message Service)First of all, please check whether you have the license to send SMS messages on your system.Incorrect USSD commands can result in blocked SIMs or failure in the mobile module!Figure 7.3 Recharging with USSD Codes!!
MOBILE CONFIGURATION OPTIONSCHAPTER 7124iGATE 15.0. Revised: 2009.You will find it in the General view under Licenses when you connect to the system via GATE Manager.Figure 7.4 GATE Manager General ViewThe name for the license is SMS. This entry is required to send SMS.You must configure the mail service in the [Mail] section of the file pabx.cfg if you want to send the SMS messageswith an e-mail client through a mail server or directly to the iGATE:[Mail]SmtpServer=<server addr>MailRcpt=<domain>MailFrom=<own address or name>The third entry in the mobile controller's Subscriber line is the SMS center number: German example: You must restart the system to activate the changes.Then enter the port-specific SMS settings: MapAllSMS<shortnumber>=LAIN*0001:<number>MapAllSMS<shortnumber>=port*0001:<number>Example: In the following German example with LAIN numbers, the short number 00 is routed to the firstThis entry is not necessary when using only the GateManager's Send SMS command.Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIMS,IMSI] CHADDR ALARMSubscriber00=TRANSPARENT ROUTER GSM[0000,00000,+491721111,1,1,1,SIMS,IMSI] CHADDR ALARMii
MOBILE CONFIGURATION OPTIONSCHAPTER 7125iGATE 15.0. Revised: 2009.controller. The number 12345 is sent to the SMS center.If the SMS is sent with a normal e-mail client, the keyword SMS will appear in the To dialog box, followed by theshort number, which indicates the mobile controller. An @ sign and the iGATE's IP address or name if the systemis attached to a DNS server will follow. The message box contains the recharge code in the carrier's syntax.SMS00@<ipaddr>SMS00@<domain>If the SMS is used with the Send SMS command in theGATE Manager's Commands menu, use only the short numberand not the keyword SMS.To save the recharge platform's confirmation e-mail, the e-mailcan be sent to an account using the following entry in theroute.cfg:Restrict<port>=@<addressee> 05It can also be saved into a file using the following entry in thepabx.cfg:MsgLog=/data/msg.logTo save it into a file, the following entry in the route.cfg is alsorequired:Restrict<port>=@FILE 05Example: In the following example for saving the SMS into a file, all incoming SMS to LAIN 26212 is savedinto the file msg.log:If the e-mail is sent to an account, the routing entry will look like this: Use the following entries in the pabx.cfg to connect the iGATE to an e-mail server:[Mail]SmtpServer=<server address>MailRcpt=<domain>MailFrom=<own address or name>MapAllSMS00=26212*0001:12345MapAllSMS01=26212*0101:12345MapAllSMS02=26212*0201:12345MapAllSMS03=26212*0301:12345MapAllSMS04=26212*0401:12345MapAllSMS05=26212*0501:12345MapAllSMS06=26212*0601:12345……Restrict26212=@FILE 05Restrict26212=@nase 05Figure 7.5 Send SMS
MOBILE CONFIGURATION OPTIONSCHAPTER 7126iGATE 15.0. Revised: 2009.7.16.3 PREPAID ACCOUNT STATUS QUERYAfter a SIM card has successfully been recharged, you can query its current account status. The following variationsare possible:Direct query via callIndirect query with the GATE ManagerListening in on the GATE Manager connectionUSSD account-status query7.16.3.1 DIRECT ACCOUNT-STATUS QUERYThe same basic settings apply here as have already been described for SIM recharging.That means routing configurations must be entered that set up a connection between the caller and the carrier'sprepaid platform. Use the same routing configuration described in Chapter 7.16.2 >. The only difference is thatyou will select the account-status query instead of account recharging from the menu. 7.16.3.2 INDIRECT ACCOUNT-STATUS QUERYThe indirect method with the GATE Manager and listening in on the connection requires a change in the patternof DTMF tones. You must, of course, know what the pattern is beforehand, and then you must configure it in theSend Call dialog. The indirect USSD account-status query corresponds with the USSD recharging procedure with altered USSD ac-count-status-query command instead of the recharging command with cash code (voucher number).The USSD recharging procedure results in an immediate USSD response message, so that the iGATE does not require an explicit query following USSD recharging.Figure 7.6 Status Queryii
MOBILE CONFIGURATION OPTIONSCHAPTER 7127iGATE 15.0. Revised: 2009.7.16.3.3 SAVING /FORWARDING THE ACCOUNT STATUSAccount-status information can be saved to a file in the iGATE. The following entry in the pabx.cfg is required:MsgLog=/data/msg.log The corresponding routing entries in the route.cfg configuration file will look like this:Restrict<port>=@FILE 06Restrict<LAIN>=@FILE 06Example: The following example shows incoming USSD messages for 2 carriers:The USSD entry in the file will appear in 2 lines as follows:Date Time [Port] IMSIUSSD Message TextExample:7.17 DEFINING SPECIAL CHARACTERS FOR VOICE CALLSIn cases in which the called number includes special characters (e.g. * or #), it may be necessary to define the calltype used in the mobile network (command or voice call). Calls to GSM or CDMA that begin with * or #, are sentas command calls by default. For voice calls beginning with * or #, you must define the call type voice in the map-ping entry with a > sign.The routing entry will look like this:MapAll<num>=<LAIN>><num>Example:Restrict26212=@FILE 06 Restrict26213=@FILE 0614.02.05-17:40:06 [04] 262125555555555 Current Cash Account: 143,83 EurosMapAll222=11111>*222
SIGNALING AND ROUTING FEATURESCHAPTER 8128iGATE 15.0. Revised: 2009.8 SIGNALING AND ROUTING FEATURES8.1 DIGIT COLLECTION (ENBLOCK/OVERLAP RECEIVING)This function makes it possible to collect up to 24 digits and transmit calls when a specific number of digits hasbeen 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 thegateway 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 totalnumber of the port digits and the digits of the called party number. This figure can range between 00 and 24 andmust be entered in double digits. The parameter DTMFWaitDial defines the number of seconds the system waitsbetween the individual digits (default 5). Please bear in mind that you can configure a maximum of 11 digits in thefirst part of the command and 19 (including a special character, e.g. #) in the second. The call will be forwardedas soon as the specified number of digits has been dialed or a time-out limit has been reached.Example: The following example shows a call with the prefix 01555. The | (pipe) signifies that the followingdigits will be collected before they are transmitted. The 14 at the end is the sum of the port digitsand the digits of the called party number (e.g. |#20=3, 01555899666=11, 3+11=14). 8.2 REJECTING DATA CALLS AND SPECIFIED NUMBERSThis chapter describes the configuration options for exclusion of data calls, prefixes, or call numbers from the rout-ing process.8.2.1 BLACKLIST ROUTINGThe system will reject all calls directly if the MapAll entry contains the keyword & followed by the two-digit causevalue (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...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 iMNP.ii
SIGNALING AND ROUTING FEATURESCHAPTER 8129iGATE 15.0. Revised: 2009.prefix 0180 are rejected with a busy signal. All other calls are sent to the VoIP profile DF: 8.2.2 WHITELIST ROUTINGThe 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 call’s origination address. Example: In the following example, the numbers 12345 and 12346 connected to the PBX at port 10 cannotmake any international calls. All national calls are sent to the VoIP profile DF and all local callsare sent to the PSTN: Example: In the following example, all incoming calls from the mobile port trunk groups 26212 and 26213are rejected with a busy signal: 8.2.3 REJECTING CALLS WITH ISDN BEARER CAPABILITY DATAISDN data calls can be handled differently from voice calls depending on the configuration of the call types DATAor 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 (switchingMapAll015551234=&91MapAll004915551234=&91MapAll0180=&91MapAll0=40DF:0...MapAll9=40DF:9A maximum of 1000 Restrict entries per time zone can be defined. Restrict1012346=intMapAllint00=&91MapAllint0=40DF:0MapAllint1=91...MapAllint9=90Restrict26212=notRestrict26213=notMapAllnot=&91Analog modm connections are not included in this configuration, as they generally do not have a specified bearer capability. iiii
SIGNALING AND ROUTING FEATURESCHAPTER 8130iGATE 15.0. Revised: 2009.equipment congestion). All calls with the prefix 0170 are routed to the mobile trunk group 26211and all other calls are routed through VoIP:8.2.4 SPECIFIC ROUTING OF DATA CALLS VIA VOIPIn the ISDN network, data calls have a special service type. When an ISDN PBX is connected to a VoIP network, itmust continue to work without any problems (e.g. PBX remote maintenance calls or ISDN terminal adapter). In thecase 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, regardlessof whether they are data calls or voice over IP calls. The first one is for outgoing voice calls andall calls from VoIP to ISDN. The second profile is exclusively for outgoing data calls, so that sig-naling consists solely of clear mode in SDP: 8.3 CLIP AND CLIR8.3.1 ROUTING CLIP AND CLIR CALLSThis function allows you to route calls with Calling Line Identification Presentation (CLIP) differently from calls withCalling Line Identification Restriction (CLIR). For example, all CLIP calls can be rejected, so that only calls that donot present the calling number or calls without a calling party number (e.g. analog) are transmitted through theiGATE.MapAll0=&aa DATA...MapAll9=&aa DATA... MapAll0170=262110170MapAll0=40DF:0...MapAll9=40DF:9MapAll0=40DATA:0 DATA...MapAll9=40DATA:9 DATAMapAll0=|40DF:0<<24...MapAll9=|40DF:9<<24Restrict40=InMapAllIn=10[Voip:DF]VoipDirection=IO...VoipCompression=g711a g729 trp t38...[Voip:DATA]VoipDirection=Out...VoipCompression=trpVoipECE=No...
SIGNALING AND ROUTING FEATURESCHAPTER 8131iGATE 15.0. Revised: 2009.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 dif-ferentiate these calls from remote administration calls. Restrict9=OK 01 means that all telephony calls without acalling 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 causewhen they are mapped to MapInFAIL=&aa. 8.4 ROUTING CALLS WITHOUT CLIRThis function enables you to bypass CLIR for calls through the defined mobile port. The following configuration inpabx.cfg activates this function:8.4.1 SETTING CLIRSetting a hash (#) in front of a call number makes it possible to suppress the presentation of the origination numberof 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 beginningwith 00491555 are sent to the port with the address 22 and the presentation of the number isrestricted:8.4.2 SETTING CLIPSetting 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....InsertCLIR=On...Restrict9=OK 01Restrict|9=OK 01Restrict90=FAIL 01...MapInOK00491555=2200491555MapInFAIL=&aa...Subscriber<xx>=...GSM[...,!CLIR]...When this function is configured, the SIM’s telephone number (and not originating telephone) is always transmitted to the B subscriber.MapAll00491555=#2200491555ii
SIGNALING AND ROUTING FEATURESCHAPTER 8132iGATE 15.0. Revised: 2009.The following sytax is used: MapAll<num>=!<port><num>Example: The following example shows an appropriate configuration. With this entry, all calls beginningwith 004930 are sent to the port with the address 9 and the presentation of the origination num-ber is allowed.:8.5 CONVERSION OF CALL NUMBERSThe conversion of call numbers makes it possible, for example, to implement number portability or to redirect callswhen the user can be reached at another number. In the following mapping command, the call number015550123456 is changed to 015559876543 and sent to the mobile channel (MapAll...=20..):Example 1Example 2 > presents an alternative, in which the routing file is searched through again after conversion of thecall number to determine the route for the prefix 01555. Please bear in mind that you can configure a maximumof 1499 mapping entries with no more than 11 digits in the first part of the command and 19 in the second.Example 28.6 SETTING NUMBER TYPE IN OAD/DADIn some cases it may be necessary to set a specific number type for the OAD or DAD. There are different methodsfor the various interfaces. The following number types can be set: OADUse the following entry to set a specific number type in the OAD:MapAll004930=!9004930...MapAll015550123456=20015559876543...MapAll015550123451=$ReceptionMapAll015550123452=$ReceptionMapAll015550123453=$ReceptionMapAllReception=015559876543Table 8.1 Number TypesType DefinitionuUnknowns Subscriber numbern National numberi International number
SIGNALING AND ROUTING FEATURESCHAPTER 8133iGATE 15.0. Revised: 2009.Restrict<port><num>=<type> 15For the national and international types, remove the 0(s) at the beginning of the number:Restrict<port>0=n 15Restrict<port>00=i 15Example: In the following example, the bit is set in the caller’s origination number for a call via BRI con-troller 01:You can set a u (unknown type of number) in the Restrict entry to change transmission of the national/internationalbit to 0 or 00 at the beginning of the OAD. As in a mapping entry, the national/international bit will always appearleft of the equal sign as 0 or 00.Restrict<port>0=u0 15Restrict<port>00=u00 15Example: In the following example, the area code 030 with a 0 at the beginning of the OAD of the PBX’sextension is set as a digit and transmitted along with the number: The keyword RestrictR allows you to set a second modification in the OAD in the case of a redirect.Example: In the first part of this example, OADs beginning with 030 are changed to 4930: If the call is not connected and a Redirect3 is configured for the call, the OAD will be changedfrom 4930 to 004930 as follows:DADEnter 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 thebeginning of the number:Restrict90=n 15Restrict900=i 15Restrict10555=u030555 15Restrict entries are handled from general to specific from top to bottom.Restrict9030=4930 15RestrictR4930=004930 15ii
SIGNALING AND ROUTING FEATURESCHAPTER 8134iGATE 15.0. Revised: 2009.Example: In the following example, the international bit is set for all calls to Italy (0039) and the numberis transmitted with 39. For the area code 012, the national bit is set and the number is transmit-ted with 12: General ExampleExample: In the following example, a 1:1 routing entry for the individual PRI controllers to VoIP appears inaddition to the international flag from PRI to VoIP. A placeholder routing entry is used (bla or blu),in which the PRI ports are directly assigned to a mapping. Traffic at PRI port 9 is sent directly toVoIP port 40 with the VoIP profile iG1. Traffic from PRI port 10 is sent to VoIP port 40 with theprofile iG2: 8.7 SETTING THE SCREENING INDICATORYou can set the screening indicator to define whether the calling-party number sent is specified as user providedverified and passed or network provided:User provided verified and passed: vExample: In the following Restrict example, the calling party number sent is specified as user provided ver-ified and passed: Network provided: pExample: 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, andMapAll0039=40iG1:i39 VOICE MapAll012=40iG1:n12 VOICERestrict9=blaRestrict900=i 15Restrict10=bluRestrict1000=i 15MapAllbla00=40iG1:iMapAllblu00=40iG2:iThe restrict entries for the individual ports must appear in the following order: placeholder, OAD international flag, DAD routing with international flag.Restrict10=v 15Restrict10=p 15ii
SIGNALING AND ROUTING FEATURESCHAPTER 8135iGATE 15.0. Revised: 2009.the number type is international: Example: Please bear in mind that this entry will not work if you set a minus sign (-) behind Voi-pOad=<num>.8.8 SETTING A DEFAULT OADUse 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 beginswith 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 re-stricted. Example: In the following example, the digits 004930 are replaced with 030 followed by the remainingdigits. The destination number begins with 030 and is sent through port 10.8.9 SETTING OR REMOVING SENDING COMPLETE BYTE IN SETUPIn some cases the ISDN or H323 peer system may require this byte for routing, or the byte may disrupt signaling. Setting Sending CompleteThe following entry ensures that the Setup includes a Sending Complete: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 controller9:Removing Sending CompleteThe 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 VoIPRestrict10=ip 15Restrict9=*12345 15MapAll030=10030Restrict9004930=030 15MapAll030=10030MapAll0=)90
SIGNALING AND ROUTING FEATURESCHAPTER 8136iGATE 15.0. Revised: 2009.controller 40. The VoIP profile is DF:8.10 EXCLUDING PREFIXES FROM VGATE COUNTERThis option allows you to exclude flat rate prefixes (e.g. fixed network calls) from the vGATE and iGATE limitcounters.8.10.1 EXCLUSION FROM SIM DAILY CALL ATTEMPTS COUNTERThe keyword CNC (call not counted) will exclude the mapping entry from the call counter:MapAll<num>=<port><num> CNC Example:8.10.2 EXCLUSION FROM SIM MINUTES COUNTERThe keyword DDNC (daily duration not counted) will exclude the mapping entry from the minutes counter:MapAll<num>=<port><num> DDNC Example:8.11 MISCELLANEOUS ROUTING METHODSIn the following scenarios it may occur that some call numbers must be routed with differing lengths or that somecall 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 number8.11.1 ROUTING CALLS WITHOUT A DESTINATION NUMBEREnter the following configuration in the route.cfg if the iGATE must route calls that come in without a destinationnumber:Restrict<port>=<pl>MapAll<pl><num>=<port><num>MapAll<pl>=<port>MapAll0=(40DF:0MapAll030=26212030 CNCMapAll030=26212030 DDNC
SIGNALING AND ROUTING FEATURESCHAPTER 8137iGATE 15.0. Revised: 2009.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 placeholder’s placeholder’s mapping.Example: In the following example, all calls from controller 9 are routed to controller 10, regardless ofwhether a destination number appears in the setup: 8.11.2 ROUTING CALLS BASED ON AN EXTENSION PREFIX OR ON THE LENGTH OF THE DESTINATION NUMBERTo route calls with a DAD differently from those without a DAD, you must activate the block feature in the pabx.cfgand restart the system:Block=1Set all other parameters in the route.cfg. First define the port from which the incoming calls are to be routed. In-coming calls from the configured port will be assigned a placeholder and then digit collection will occur for all callsbeginning with the placeholder. The $ in the mapping entry, followed by the defined placeholder (MMM), causesa second search of the routing file when the number is complete:DTMFWaitDial=<sec>Restrict<port>=<pl>MapAll<pl>=|$MMM<<98The 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 withthe 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 VoIPwith the SIP account Al. All other calls with a destination number are sent to controller 10. Callswithout a destination number are sent to the number 12345 at port 10:Restrict9=plMapAllpl=10DTMFWaitDial=5Restrict9=plMapAllpl=|$MMM<<98MapAllMMM2222=40DF:BettyMapAllMMM3333=40DF:AlMapAllMMM0=100MapAllMMM1=101MapAllMMM2=102MapAllMMM3=103MapAllMMM4=104MapAllMMM5=105MapAllMMM6=106MapAllMMM7=107MapAllMMM8=108MapAllMMM9=109MapAllMMM=1012345
SIGNALING AND ROUTING FEATURESCHAPTER 8138iGATE 15.0. Revised: 2009.8.12 CHANGING CAUSE VALUESIt is possible to group cause values together into a single defined cause value so that rejected calls can be handledin a specified manner by the switch sending the call to the iGATE. The following cause value groups can be definedin the pabx.cfg:Group 0 Cause ValuesAll connections that are rejected with a group 0 cause value (0x80-0x8f) can be mapped to a single cause valueby entering TranslateG0Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.Group 1 Cause ValuesAll connections that are rejected with a group 1 cause value (0x90-0x9f) can be mapped to a single cause valueby entering TranslateG1Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.Group 2 Cause ValuesAll connections that are rejected with a group 2 cause value (0xa0-0xaf) can be mapped to a single cause valueby entering TranslateG2Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.Group 3 Cause ValuesAll connections that are rejected with a group 3 cause value (0xb0-0xbf) can be mapped to a single cause valueby entering TranslateG3Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.Translating Individual Cause ValuesThe following parameter allows you to translate any of these cause values to any other one: Trans-late<cause>=<cause>. The values entered must be in hexadecimal notation between 00 and 7f.Translating SIP Causes to ISDN and Vice VersaYou can define a specific translation from SIP responses (4xx - 6xx) to ISDN cause values and vice versa. If nothingis set, the translation occurs as described in draft-kotar-sipping-dss1-sip-iw-01.txtUse 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)
ADDITIONAL VOIP PARAMETERSCHAPTER 9139iGATE 15.0. Revised: 2009.9 ADDITIONAL VOIP PARAMETERSYou can enter the following additional parameters in the route.cfg to adjust the configuration for improved com-munication with the VoIP peer.9.1 SIGNALING PARAMETERS Table 9.1 Customized Parameters: Protocol-Independent VoIP Signaling Protocol-Independent VoIP Signaling ParametersVoipDad=<num>The digits/numbers defined here will appear in front of the original DAD as described for the parameter VoipOad below. If the parameter is to be valid in only one direction, you must also set the parameter Voip-DadIn or VoipDadOut .VoipOad=<num>In the following examples, the OAD is 5175551212.The digits/numbers defined here will be transmitted in front of the original OAD. In the followingexample, 001 will appear in front of the number 5175551212.EXAMPLE: VoipOad=001To transmit only OADs consisting of fewer digits than those defined, enter a !, followed by the numberof digits, at the end of the entry. If the OAD has fewer digits, it will be transmitted unchanged. If it hasthe same number or more digits, only the string in front of the ! will be transmitted. In the followingexample, only the digits 001 will appear:EXAMPLE: VoipOad=001!10If a minus (-) is entered, the original OAD will not appear. In the following example, no number will betransmitted.EXAMPLE: VoipOad=-If an integer is entered before the minus sign, only the number of digits entered in front of the minussign will be displayed. In the following example, 517555 will appear.EXAMPLE: VoipOad=6-If an integer is entered after the minus sign, this number of digits will be removed from the beginningof the OAD. In the following example, 517 will be removed from the OAD:EXAMPLE: VoipOad=-3If -/ is entered followed by the first part of an OAD, that part will be removed. If the string does notmatch, the OAD will be transmitted unchanged. In the following example, only 1212 will be transmitted.EXAMPLE: VoipOad=-/517555To modify the original OAD, enter random<x>, whereby x represents a number of random digitsbetween 1 and 10 that will appear in the OAD. In the following example, 001 plus 2 random digits plusthe original OAD will appear.EXAMPLE: VoipOad=001random2NOTE: If the parameter is to be valid in only one direction, you must also set the parameter Voi-pOadIn or VoipOadOut .
ADDITIONAL VOIP PARAMETERSCHAPTER 9140iGATE 15.0. Revised: 2009.VoipDadIn=<string>Specifies that the parameter VoipDad is for incoming calls only. If this parameter is not set (default), VoipDad will apply for both directions.VoipDadOut=<string>Specifies that the parameter VoipDad is for outgoing calls only. If this parameter is not set (default), VoipDad will apply for both directions.VoipOadIn=<string>Specifies that the parameter VoipOad is for incoming calls only. If this parameter is not set (default), VoipOad will apply for both directions.VoipOadOut=<string>Specifies that the parameter VoipOad is for outgoing calls only. If this parameter is not set (default), VoipOad will apply for both directions.VoipProgress=<int>For H.323: 0=progress indicator is not transmitted. 1 (default)=progress indicator is transmitted. 2=address complete message is transmitted. 3=call proceeding message type changed in alerting message type.For SIP: 0=183 response ignored and not sent. 1=183 response changed to a progress message with inband-info-available at the ISDN interface (default). 2=183 response changed to an address complete message at the ISDN interface. 3=183 response changed to an alerting at the ISDN interface.VoipConnectOnCallProc=<mode>Enter Yes (default No) to change an H.323 Call Proceeding/Call Progress and Alert, or a SIP 180 or 183, into an H.323 Connect or SIP 200 message. This parameter can be used if an announcement that plays before the Connect requires a Connect on the other side to put through the call.VoipComprMaster=<mode>This parameter defines which side the first matching codec comes from:Yes: Default. Priority is determined by the order of the system’s parameter list.No: Priority is determined by the peer.VoipHideOadByRemove=<mode>If Yes is configured and call setup is to VoIP, the OAD will be removed from signaling if presentation restricted or user-provided, not screened is set in the calling party’s presentation or screening indicator. No (default) means no change will occur.NOTE: If the SIP protocol is used, Anonymous will always appear as the account in the From field. Transmission of the OAD can occur in the P-asserted header.Table 9.1 Customized Parameters: Protocol-Independent VoIP Signaling (continued)Protocol-Independent VoIP Signaling Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9141iGATE 15.0. Revised: 2009.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 VoipCompres-sion=<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.Table 9.1 Customized Parameters: Protocol-Independent VoIP Signaling (continued)Protocol-Independent VoIP Signaling Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9142iGATE 15.0. Revised: 2009.Table 9.2 Customized Parameters: H.323 Signaling H.323 Signaling ParametersVoipService=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 7kHz201 - Fax 2 202 - Fax 3 203 - Fax 4 700 - DataNormally 101 is used. You can send another value to a switch that wants to handle VoIP calls differently from PSTN calls.EXAMPLE:VoipService=0x101VoipMapAddressType=<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.
ADDITIONAL VOIP PARAMETERSCHAPTER 9143iGATE 15.0. Revised: 2009.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.VoipRejectIncomingNonMatchingFaststart=<mode>Setup will be rejected if the RTP codecs offered for incoming H.323 call setup with Faststart elements do not match those configured in the parameter VoipCompression. Default No.VoipMCinRLC= <mode>Enter Yes to cause the system to send the media channel capability in the reverse logical channel parameters as part of the H.245 negotiation (default No).Table 9.3 Customized Parameters: SIP Signaling SIP Signaling ParametersVoipOwnAddress=<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.If the keyword IMSI appears in the parameter and the call is from GSM to VoIP, the SIM cards IMSI is trans-mitted in the FROM field:EXAMPLE: VoipOwnAddress=IMSI@iGATE01VoipOwnDisplay=<string>The entry is sent as Display Name in the From Field in SIP transmissions. The keyword MSN causes the calling telephone’s MSN to be transmitted as Display Name. The keyword DSP causes the ISDN display information element to be transmitted as Display Name. Default: no setting.Example: From: "John" <sip:493011111@teles.de>VoipUserAgent=<mode>/<string>When Yes is set (default), the system type and software version is used in the SIP user agent header. Enter no to deactivate this setting, or enter a string to change it.VoipContact=<account@domain>Used for the Contact field in Sip-Invite and Sip-Response messages.VoipContactParam=<string>Sets additional header parameters in the contact field.Table 9.2 Customized Parameters: H.323 Signaling (continued)H.323 Signaling Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9144iGATE 15.0. Revised: 2009.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 is transmitted.<string> The defined string is transmittedA combination of both is possible. Examples: 030* or tel:* or sip:user@carrier.deVoipP-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 transmittedA combination of both is possible. Examples: 030* or tel:* or sip:user@carrier.deVoipOadSource=<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-ID2 = P-Preferred-Identity4 = P-Asserted-IdentityNOTE: If 2 or 4 are entered, the number in the field must begin with tel:Going to SIP, the OAD is written in the following field:0 = From: field (default)1 = Remote-Party-ID (if VoipOwnAddress is not set)For the fields P-Preferred-Identity and P-Asserted-Identity, please check the corresponding parameters. If the number is sent with CLIR to SIP, the From: field contains anonymous@anonymous.invalid. If the number has to appear in the From: Field, the decimal value of the parameter must be increased by 8.VoipDadSource=<int>SIP only: defines the field from which field the called party number coming from SIP is to be taken:0 = URL or URI in the Invite request (default)1 = To: field2 = Remote-Party-ID with party = calledVoipUseMaxPTime=<mode>SIP only. Enter yes to set the field mptime (max packet time) with the values set in VoipTxm (ptime). Default no.The parameter VoipUseMaxPTime is used when VoipUseMPTime is 0, 1 or 2.Table 9.3 Customized Parameters: SIP Signaling (continued)SIP Signaling Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9145iGATE 15.0. Revised: 2009.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 with over-lap 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 URI’s available digits or to the invite message’s To field. No (default) means that the digit contents of the SubsequentNumber field will be used.VoipAllow=<list>The allow header shows the supported methods and can be set here.EXAMPLE: VoipAllow=INVITE,BYEThe default setting includes the following:INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFERIt 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 param-eter to Yes if you use the parameter VoipMaxChan.VoipAckWithSdp=<mode>Enter yes to send the SDP content in the SIP ack message. Default no.Table 9.3 Customized Parameters: SIP Signaling (continued)SIP Signaling Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9146iGATE 15.0. Revised: 2009.9.2 REGISTRAR PARAMETERSThe following parameters can be used in the VoIP profile when the SIP agent wants to register with the iGATE. Example: The following example creates an account for a user agent with the username 130 and passwordtest130. Authentication occurs with the procedure www:Table 9.4 Customized Parameters: Location Server Location Server ParametersVoipOwnUser=<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 agent’s registration applies (default 3600).VoipAuth=<mode>Defines the authentication procedure www (default) or proxy.MapAll130=40U1:130[Voip:U1]VoipDirection=IOVoipIpMask=0x00000000VoipOwnUser=130VoipOwnPwd=test130VoipExpires=300VoipAuth=wwwVoipCompression=g711a g711u g729 g729a g729b g729ab VoipSilenceSuppression=noVoipSignalling=1VoipMaxChan=8VoipTxM=2VoipDtmfTransport=0VoipRFC2833PayloadType=101VoipMediaWaitForConnect=Tone
ADDITIONAL VOIP PARAMETERSCHAPTER 9147iGATE 15.0. Revised: 2009.9.3 ROUTING PARAMETERSTable 9.5 Customized Parameters: VoIP Routing VoIP Basic ParametersVoipOadMask=<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 com-pany, 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. De-fault 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 firewall’s 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 iGATE’s private IP address.
ADDITIONAL VOIP PARAMETERSCHAPTER 9148iGATE 15.0. Revised: 2009.9.4 QUALITY PARAMETERSTable 9.6 Customized Parameters: VoIP Quality VoIP Quality ParametersVoipSilenceSuppression=<mode>Activates silence suppression (see Table 5.21 >). 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.17 >.VoipMediaWaitForConnect=<mode>This parameter allows you to influence the system’s 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, release). 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 controller’s 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 9.7 >. 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 9.7 >. 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).
ADDITIONAL VOIP PARAMETERSCHAPTER 9149iGATE 15.0. Revised: 2009.VoipPCMPacketInterval=<int>This parameter changes the default interval for PCM codecs (G.711, G.726). That means the VoipTxm factor is muliplied using this interval:For 16-channel chips:0 = 20ms (default)1 = 5 ms2 = 10 ms 3 = 20 msFor 8-channel chips:0 = 10ms (default))1 = 5 ms2 = 10 ms 3 = 20 msVoipCallGroup=<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 broken ex-ists for the number of seconds entered (default 90). If 0 is entered, no entry will be generated and the con-nection will not be terminated.Table 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9150iGATE 15.0. Revised: 2009.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. 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 (default 0). This parameter is necessary to set up an IntraSTAR call immediately when the IP connection is disrupted. Bear in mind that VoipSilenceSuppres-sion=No must appear in the VoIP profile. 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. When No is set, RTP packets sources other than those recognized are rejected. Default No. Table 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9151iGATE 15.0. Revised: 2009.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 19Gain Slope:0 - 00.25dB1 - 00.50dB2 - 00.75dB3 - 01.00dB4 - 01.25dB5 - 01.50dB6 - 01.75dB7 - 02.00dB8 - 02.50dB9 - 03.00dB10 - 03.50dB11 - 04.00dB12 - 04.50dB13 - 05.00dB14 - 05.50dB15 - 06.00dB16 - 07.00dB17 - 08.00dB18 - 09.00dB19 - 10.00dB20 - 11.00dB21 - 12.00dB22 - 13.00dB23 - 14.00dB24 - 15.00dB25 - 20.00dB26 - 25.00dB27 - 30.00dB28 - 35.00dB29 - 40.00dB30 - 50.00dB31 - 70.00dBTable 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9152iGATE 15.0. Revised: 2009.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 or mobile. The range is 0-63. The default value of 32 is 0 dB.Table 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9153iGATE 15.0. Revised: 2009.VoipQualityCheck=<type minsamples limit recovertime>type Enter one of the following: ASR1, ASR2, RoundTripDelay, Jitter or FractionLostWhen type is ASR1 or ASR2:minsamplesMinimum number of calls for which ASR shall be calculated with:limitA value between 0 and 100 recovertimeSeconds to block the profile.When type is RoundTripDelay:minsamplesMinimum number of seconds RTD must be above:limitThe highest acceptable value for RTD (in milliseconds)recovertimeSeconds to block the profile.When type is Jitter:minsamplesMinimum number of seconds jitter must be above:limitThe highest acceptable value for jitter (in milliseconds)recovertimeSeconds to block the profile.When type is FractionLost:minsamplesMinimum number of seconds FL must be above:limitThe highest acceptable value for FL (percentage between o and 100)recovertimeSeconds to block the profileNOTE: If you base VoipQualityCheck on the ASR values: During setup, calls are calculated as not connected, 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.Table 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9154iGATE 15.0. Revised: 2009.The following specifications for Quality of Service correspond with RFC791 and RFC1349.VoipEcl=<ms>This parameter defines the required tail length for echo cancelation. The following values in ms are possible:3264 (default)128VoipT301=<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 carrier’s service fails.EXAMPLE:Redirect340DF:=AMapAllA=9[Voip:DF].....VoipT303=5VoipT304=<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 9.7 Quality of Service Values Bit Distribution01234567Precedence TOS MBZBit Description0-2 Precedence3 TOS: 0=normal delay, 1=low delay4 TOS: 0=normal throughput, 1=high throughput5 TOS: 0=normal reliability, 1=high reliabilityTable 9.6 Customized Parameters: VoIP Quality (continued)VoIP Quality Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9155iGATE 15.0. Revised: 2009.9.5 COMPRESSION PARAMETERSThe following parameters are for RTP multiplexing, which aggregates RTP packets (voice user data) for individualVoIP calls into a packet. The header (for Ethernet, IP, UDP and RTP) is sent only once for all calls instead of for eachindividual 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 cost7 MBZ: must be 0 (currently not used)Precedence Description111 Network control110 Internetwork control101 CRITIC/ECP100 Flash override011 Flash010 Immediate001 Priority000 RoutineTable 9.8 Customized Parameters: VoIP Compression VoIP Compression ParametersVoipAggRemoteRtpPort=<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=29500Enter the port for the VoIP peer that is used for aggregated packets (compressed data). Default: 29500.VoipAggOwnDataPort=<port>VoipAggOwnDataPort=29500Enter the own port number used for aggregated packets. Default: 29500.VoipAggRemoteRtpPortSpacing=<count>Defines the space between the ports used for the peer’s individual RTP streams (default 2).Table 9.7 Quality of Service Values (continued)
ADDITIONAL VOIP PARAMETERSCHAPTER 9156iGATE 15.0. Revised: 2009.9.6 FAX/MODEM PARAMETERS Table 9.9 Customized Parameters: VoIP Fax VoIP Fax/Modem ParametersVoipFaxTransport=<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 transmit-ted using T.38.VoipFaxBypassPayloadType=<num>Defined the payload type for a fax’s 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/sec1 - 48002 - 72003 - 9600 (default)4 - 120005 - 14400EXAMPLE:VoipFaxMaxRate=5VoipFaxECM=<mode>You can use this parameter to enable the error correction mode for fax transmission: yes=enabled, no=disabled (default).VoipAPartyCanSwitchToT38=<mode>Enter Yes (default) to activate fax detection in both directions. When No is set, fax detection and translation to T.38 are carried out only when the call comes from VoIP.VoipSuppressInitialT38Signalling=<mode> (SIP only)Enter Yes to suppress the SDP header m=image t38 in all SIP messages until reinvite of the actual fax detec-tion occurs (default No).VoipFaxDisableAfterConnect=<sec>Deactivates fax detection after the number of seconds entered has passed. This is intended to avoid conver-sional disruption resulting from fax transmission noises when a fax machine is next to a phone that has an established call.The following parameters are responsible for setting the modem transport method if a modem connection is de-tected.
ADDITIONAL VOIP PARAMETERSCHAPTER 9157iGATE 15.0. Revised: 2009.VoipV21Transport=<mode>0=disabled (must be set to 0).VoipV22Transport=<mode> 0=disabled (default), 2=bypass.VoipV23Transport=<mode> 0=disabled (default), 2=bypass.VoipV32Transport=<mode> 0=disabled (default), 2=bypass .VoipV34Transport=<mode> 0=disabled (default), 2= bypass.Table 9.9 Customized Parameters: VoIP Fax (continued)VoIP Fax/Modem Parameters
ADDITIONAL VOIP PARAMETERSCHAPTER 9158iGATE 15.0. Revised: 2009.9.7 DTMF PARAMETERSTable 9.10 Customized Parameters: VoIP DTMF VoIP DTMF ParametersVoipIBSDetectDir=<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, set VoipDtmfTransport to 1 or 3. NOTE: If 1 is entered, fax detection is not supported.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 inband0 = 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.VoipComprDtmfInband=<list>This parameter always forced DTMF-tone inband transmission for the configured voice codes, regardless of what is configured for: VoipDtmfTransport=. The same codecs can be configured as for VoipCompres-sion=<list>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10159iGATE 15.0. Revised: 2009.10 SYSTEM MAINTENANCE AND SOFTWARE UPDATE10.1 CONFIGURATION ERRORSWhen typographical errors are made in the configuration files, an entry appears in the protocol.log when theconfiguration is activated. This entry includes the line number and its contents.10.2 STATUS AND ERROR MESSAGESThe 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 seethat all activities are recorded beginning with the date and time. If functions were activated by key combinationsfrom terminal devices you can identify these along with the service ID.16.05.06-11:51:31,[990]Start STATUS - TELES.iGATE 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.216.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 10.1 Event Log Messages Message NMS DefinitionStatus 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 ChangesActivate configuration <num> OKConfiguration <num> successfully loaded. Initiator displayed in next line.Activate configuration <num> failed [<err>]Configuration <num> could not be loaded.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10160iGATE 15.0. Revised: 2009.Remote Control: Date & Time changedDate and/or time were changed via remote administration.Time Switch Operation The configuration change was made by the timer.Remote AdministrationRemote Control from <peer>, <RemoteCode>, <service>, 0Remote administration access from number or IP address.Remote Control: OK Successful remote administration access.[993]Remote Control: wrong passwordX Remote administration access was denied because of a wrong pass-word.[994]Remote Control: wrong numberX 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>, 0Remote administration session from <num> ended. Session length is indicated by start time and end time.Errors Reported by the Status ProgramTable 10.1 Event Log Messages (continued)Message NMS Definition
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10161iGATE 15.0. Revised: 2009.The following options are available for monitoring the iGATE 4 Mobile Boards’ status or the status of each mobilechannel. You can access status information through data recorded in the protocol.log file or in the Layer 1column in the GATE Manager’s Port Status window.[<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)If the error persists, 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 Callback-Call <num> ArrivedCallback 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).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 hard-ware 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 10.1 Event Log Messages (continued)Message NMS Definition
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10162iGATE 15.0. Revised: 2009.Table 10.2 Status Entries Definition Protocol Log GATE Managermobile channel is in initializing phase initialisingSIM card carrier module has not been insertedERR: SIM-Card not reg., no simPower supply to the iGATE 4 Mobile Board is not availablenot reg., no powerSIM card could not log on because of in-correctly configured PINwrong PIN 1xwrong PIN 2xSIM card is logged on, mobile channel is notnot reg.SIM card is logged on, mobile channel is searching for a base stationsim existsSIM card is logged on, but barred (e.g. insufficient field strength) Barred reg.barredSIM card is logged on, mobile channel registers as roamingERR: OK roamingSIM card is logged on, mobile channel is logged onERR: OK registeredNo SIM card detected or inserted ERR: layer 1 no SIMSIM card is logged off, mobile channel is logged offERR: layer 1 on holdNo mobile channel was available for the call.ERR: No ChanValues have fallen below the parame-ter’s settings; the Mobile channel will be restarted.ERR: ASR
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10163iGATE 15.0. Revised: 2009.The following status and error messages appear in the protocol.log file when ALARM appears in the VoIPport’s subscriber line: Table 10.3 Protocol Log Status and Error Messages Message DefinitionSystem 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 controller’s 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 activedown Ethernet link is inactive!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 without 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.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10164iGATE 15.0. Revised: 2009.GK <name> GRJ <num> GatekeeperRequest was rejectedGK <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>: registration 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>: registration forbidden Registration with specified registrar is not allowed.registrar <name> not answering Specified registrar does not respond.voipconn oad->dad broken Voice codec chips report broken RTP connection.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 addr> Connection to the iMNP reestablished. Table 10.3 Protocol Log Status and Error Messages (continued)Message Definition
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10165iGATE 15.0. Revised: 2009.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.Configuration Errors in the ip.cfgError in ip.cfg line <line>: section [<section_name>] unknownError in ip.cfg line <line>: parameter "<parameter_name>" in [<section_name>] unknownError in ip.cfg line <line>: parameter "<parameter_name>" does not belong to any SectionThere is an error in the NAT ConfigurationThe NAT was not loaded, please check the Configuration for mistakesThere is an error in the DHCPD ConfigurationThe DHCP SERVER was not loaded, please check the Configuration for mistakesThere is an error in the ALTQD ConfigurationThe ALTQD SERVER was not loaded, please check the Configuration for mistakesThere is an error in the FIREWALL ConfigurationThe FIREWALL was not loaded, please check the Configuration for mistakesError in <dsl_interface> Connection failed. Please, connect a cable in the <ethernet> portError in <dsl_interface>: Connection Failed. Please, revise your Username/Password configurationError in <dsl_interface>: Connection Failed. Please, revise the DSL ModemTable 10.3 Protocol Log Status and Error Messages (continued)Message Definition
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10166iGATE 15.0. Revised: 2009.10.3 SOFTWARE UPDATEYou 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 basicsoftware consists of the following files:startnetbsdznetbsdfs.gzand one of the following:iGATE GSM: igate.tz1oriGATE CDMA: cgate.tz1oriGATE UMTS: igate.tz1Make sure there is enough available memory for the new version. We recommend that you delete unnecessary logfiles and back-ups. Do NOT delete or rename existing software files before updating. Once the files have been completely transferred, check the file size and reboot the system. As soon as you can reachthe system via GATE Manager again, check the version number of the running software.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.!!ii!!ii
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10167iGATE 15.0. Revised: 2009.An update of the following optional function modules (see Chapter 12 >) occurs in the same way. Make sure thefile extension has the same running number as that of the file on the system:GUI:httpd.tz2httpd.izgDNS forwarder:dnsmasg.tz2SNMP agent:snmpd.tz0IP update:ipupdate.tz2The only exception is that you must shut down the modules that have *.izg files before updating. To shut downthese 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.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10168iGATE 15.0. Revised: 2009.10.4 TRACEDuring operation, the trace readouts of the iGATE can be saved in a file or transmitted with remote maintenancedirectly. The trace options must be turned on in the GATE Manager (offline or online trace) or via FTP raw com-mands (see Chapter 4.12.3 >). Trace results presented here are for PRI,VoIP, GSM/CDMA/UMTS interfaces andfor the following services in various levels:Figure 10.1 GATE Manager: Offline Trace Activation WindowiGATEs offer two different types of trace:Online - trace information is immediately displayed in the GATE Manager’s trace window.Offline - trace information is written to a file on the iGATE.Table 10.4 Trace OptionsOption DefinitionMail 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.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10169iGATE 15.0. Revised: 2009.iGATE systems create trace files when the TraceLog=file entry is present in the pabx.cfg. Traces can be activatedvia remote administration (GATE Manager or FTP). Trace Output FormatThe 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 secondsTraces appear in the following format:[<hh:mm:ss>] <module>[<port>]: <trace><module> – s = send for PRI/BRI or mobile ports– r = receive for PRI/BRI or mobile 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,mobile)– 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 moduleTable 10.5 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.ii
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10170iGATE 15.0. Revised: 2009.10.4.1 ISDN TRACE OUTPUTTrace output for DSS1 are in hexadecimal notation. You can use the external tool TraceView.exe to translate offlinetrace output. You will find the tool in the Software folder on the enclosed CD. The GATE Manager’s trace windowcan also display translated online traces.Example: The following example shows an untranslated DSS1 trace: 10.4.2 GSM/CDMA/UMTS TRACE OUTPUTThe trace output for GSM appears in hexadecimal notation. Its format is the same as that for ISDN output. Table10.6 > and Table 10.7 > describe the contents of GSM trace output. 17.05.06-09:54:40,Start 11.7a (L3)[09:55:14.58] r[00]: 00 01 02 02 08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 6c 02 81 31 70 06 81 31 32 33 34 35 7d 02 91 81 [09:55:14.58] s[00]: 02 01 02 04 08 02 80 02 0d 18 03 a9 83 81 [09:55:14.58] s[01]: 00 01 a8 9a 08 02 00 46 05 04 03 80 90 a3 18 03 a1 83 89 6c 02 81 31 70 06 81 31 32 33 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,EndTable 10.6 Request Messages to the GSM Module Hex Value Description00 Setup01 Connect02 Disconnect03 SMS04 DTMF05 Set Config06 Get Config07 LED08 Restart09 Switch SIM
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10171iGATE 15.0. Revised: 2009.Example: The following example shows a GSM call through the fourth GSM controller:10.4.3 VOIP TRACE OUTPUTAs described above in Chapter 10.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.Table 10.7 Incoming, Indication Message from the GSM Module Hex Value Description0B Alert0C Voice Indication0D Connect0E DTMF0F Setup10 Disconnect11 SMS12 SMS Confirmation13 Error16 Get Config Confirmation18 Dial-End Call Proceeding19 USSD1A Restart IndicationStatus Request[14:57:51.80] s[04]: 06Status Information: [14:57:51.80] r[04]: 16 Setup Request:[14:57:52.29] s[04]: 00 4c 93 04 00 00 00 35 36 36 37 00 35 38 2c 36 34 36 2c 33 30 2c 2c 2c 30 2c 2c 2c 30 2c 32 36 32 2c 30 37 2c 00 72 64 09 75 70 20 7b 64 35 7d 20 27 2e 2e 2b 43 43 45 44 3a 20 32 36 32 2c 30 37 2c 34 Dial End:[14:57:55.47] r[04]: 18 Alert:[14:57:55.63] r[04]: 0b Connect Indication:[14:57:56.63] r[04]: 0d Disconnect Request:[14:59:54.13] s[04]: 02 4c 93 00 Disconnect Indication:[14:59:54.19] r[04]: 10
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10172iGATE 15.0. Revised: 2009.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.323output and are described in the following tables. For ENUM, please refer to Chapter 10.4.3.5 >.In general, the following rules apply for this trace output: The information is thoroughly analyzed where it is received (all rcv messages). 10.4.3.1 INTERFACE IP NETWORKEstablish H.323 SessionUsually there is trace output that displays a new H.323 session. The direction is crucial (whether the call is goinginto or coming out of the IP network).Table 10.8 H.323 Output Packet Descriptionh225 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.h225connect to <ip address> cr <cr> s <si>h225accept from <ip address> s <si>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10173iGATE 15.0. Revised: 2009.H.225 Signaling OutputThe following trace results are for a call coming from the IP network. rcv will appear at <dir> and signifies thedirection: Table 10.9 H.323 Session Trace Output Descriptionconnect to Outgoing VoIP callaccept from Incoming VoIP call<ip address> Peer's IP addresscr <cr> Call reference (corresponds with the internal protocol interface's PSTN call reference)s <si> Session IDh225<dir> tpkt msg 0x<mt> h225cr <cr> addr <ip address>Table 10.10 H.225 Signaling Trace Output Description<mt> The ETS message type in hexadecimal; can consist of values listed in Table 10.11 >.<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.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10174iGATE 15.0. Revised: 2009.The following lines show the packet contents in detail:Table 10.11 ETS Message Types Hex Value Message Type1 Alerting2 Call Proceeding3Progress5 Setup7 ConnectD Setup Acknowledge5A Release Complete62 Facility6E Notify7B Information7D Statush225 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 10.12 Incoming VoIP Calls Trace Output Description<mt> Message type in hexadecimal as per ETS standard (see Table 10.11 >) 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 10.13 >).FS<bool> FastStart offered in the signaling packet or not.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10175iGATE 15.0. Revised: 2009.(<codec>, Lists codecs offered (seeTable 10.34 >).<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).Table 10.13 Compression Codecs Used Synonym CodecA G.711Alaw64kB G.711Ulaw64kCG.7231DG.728EG.729FgsmFullRateGT.38faxOG.729AP G.72616Q G.72624R G.72632SG.729BTG.729ABUG.729ETable 10.12 Incoming VoIP Calls (continued)Trace Output Description
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10176iGATE 15.0. Revised: 2009.When the call is sent in the direction of the IP network, the trace will include only the most important information: Or:VG.723LW TransparentXG.721YiLBC20ZiLBC30h225<type> <mt1> dad <num> cr <cr>Table 10.14 Calls to the IP Network 1 Trace Output Description<mt> Message type written out; if a decimal number appears here, it will be translated as per Table 10.11 >.<num> Called party number.<cr> Call reference.h225<type> callproc typ <mt> cr <cr>Table 10.15 Calls to the IP Network 2 Trace Output Description<mt> The ETS message type in hexadecimal.<cr> Call reference.Table 10.13 Compression Codecs Used (continued)Synonym Codec
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10177iGATE 15.0. Revised: 2009.RTP/RTCP OutputThe RTP/RTCP output displays whether the signaling information corresponds with the contents of the compressionchips. The output occurs when a media channel is set up or torn down: rtp start cr <cr> ch <ch> li <li> ri <ri> st <st> fx <fx> cp <comp> txm <factor>Table 10.16 RTP/RTCP Output Trace Output Description<cr> Call reference.<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 re-ceive and send.<fx> 1 appears when T.38 (fax) is used, otherwise 0.<comp> The codec used, as per Table 10.13 >.<factor> Multiplication factor for default frame size (20ms, 30 ms for G.723).rtp stop cr <cr>1 ch <ch>Table 10.17 RTP Stop Message Trace Output Description<cr> Call reference.<ch> The internal media channel used.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10178iGATE 15.0. Revised: 2009.The following output shows the jitter buffer status:Table 10.18 RTP Packet Statistics Trace Output Description<ch> The internal media channel used.<byte> The call's received or sent bytes.rtcp <ch>: SR <dir> pc <pc> oc <oc> ji <ji> rt <rt> fl <fl> cl <cl>Table 10.19 RTCP Packet Statistics Trace Output Description<ch> The internal media channel used.SR<dir> Rx sender report (received) is more interesting, since it comes from the peer. Tx sender report (transmitted).<pc> Packet count (number of packets transmitted/received).<oc> Octet count (number of octets transmitted/received).<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 n8Table 10.20 Jitter Buffer Status Trace Output Descriptionn1 SteadyStateDelay in milliseconds
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10179iGATE 15.0. Revised: 2009.An RTP connection has ended when the following trace output appears:The following output results when the codec changes for a fax connection: n2 NumberOfVoiceUnderrunn3 NumberOfVoiceOverrunn4 NumberOfVoiceDecoderBfi (bfi = bad frame interpolation)n5 NumberOfVoicePacketsDroppedn6 NumberOfVoiceNetPacketsLostn7 NumberOfIbsOverrun (ibs = in band signaling)n8 NumberOfCasOverruna[<controller>]: <VoIPcodecChipType> stop ch=<ch>Table 10.21 RTP Stop Message (VP Module) Trace Output Description<ch> The internal media channel used.a[<controller>]: ac49x ch <ch> fax/data n1 n2 n3Table 10.22 Codec Change for Fax Trace Output Descriptionn1 Fax bypass flag:0Voice, data bypass or fax relay1Fax bypassn2 Signal detected on decoder output (see Table 10.23)n3 Signal detected on encoder input (see Table 10.23)Table 10.20 Jitter Buffer Status (continued)Trace Output Description
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10180iGATE 15.0. Revised: 2009.Fax relay is activated for the corresponding channel: Table 10.23 faxordatasignalevent Value Definition Description0 SILENCE_OR_UNKNOWN Undefined (unknown signal or silence)1 FAX_CNG CNG-FAX (calling fax tone, 1100 Hz)2 ANS_TONE_2100_FAX_CED_OR_MODEMFAX-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 flags7 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 mo-dem)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 session14 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 Hz18 TTY TTY19 FAX_DCN FAX-DCN (G.3 fax disconnect signal)a[<controller>]: Ac49xActivateFaxRelayCommand(1) ch <ch> rc <cr>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10181iGATE 15.0. Revised: 2009.The following output shows various values for fax transmission (see Table 10.24 for a description of the values): a[<controller>]: ac49x ch <ch> faxrelay: n1 n2 n3 n4 n5 n6 n7 n8 n9 n10 n11 n12 n13 n14Table 10.24 Fax Status Value Descriptionn1 UnableToRecoverFlag (0 no, 1 yes)n2 IllegalHdlcFrameDetectedFlag (...)n3 FaxExitWithNoMcfFrameFlagn4 HostTransmitOverRunFlagn5 HostTransmitUnderRunFlagn6 InternalErrorFlagn7 ReceivedBadCommandFlagn8 TimeOutErrorFlagn9 TxRxFlag (0 receive, 1 transmit)
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10182iGATE 15.0. Revised: 2009.n10 T30State0 FAX_RELAY_T30_STATE__INITIALIZATION1 FAX_RELAY_T30_STATE__CNG2 FAX_RELAY_T30_STATE__CED3 FAX_RELAY_T30_STATE__V214 FAX_RELAY_T30_STATE__NSF5 FAX_RELAY_T30_STATE__NSC6 FAX_RELAY_T30_STATE__CSI7 FAX_RELAY_T30_STATE__CIG8 FAX_RELAY_T30_STATE__DIS9 FAX_RELAY_T30_STATE__DTC10 FAX_RELAY_T30_STATE__NSS11 FAX_RELAY_T30_STATE__TSI12 FAX_RELAY_T30_STATE__DCS13 FAX_RELAY_T30_STATE__CTC14 FAX_RELAY_T30_STATE__CRP15 FAX_RELAY_T30_STATE__DCN16 FAX_RELAY_T30_STATE__PRE_MESSAGE_RESPONSE17 FAX_RELAY_T30_STATE__POST_MESSAGE_RESPONSE18 FAX_RELAY_T30_STATE__POST_MESSAGE_COMMAND19 FAX_RELAY_T30_STATE__VXX20 FAX_RELAY_T30_STATE__TCF21 FAX_RELAY_T30_STATE__IMAGEn11 NumberOfTransferredPagesn12 BadInputPacketIdn13 BadInputPacketTotalSizen14 FaxBitRate1 FAX_BIT_RATE__300_BPS2 FAX_BIT_RATE__2400_BPS3 FAX_BIT_RATE__4800_BPS4 FAX_BIT_RATE__7200_BPS5 FAX_BIT_RATE__9600_BPS6 FAX_BIT_RATE__12000_BPS7 FAX_BIT_RATE__14400_BPSTable 10.24 Fax Status (continued)Value Description
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10183iGATE 15.0. Revised: 2009.The following output appears when the compression chip recognizes DTMF tones:10.4.3.2 INTERNAL PROTOCOL INTERFACE (TO ISDN, MOBILE)These trace outputs always begin with the keyword pstn, followed by the direction and the message type. Themessage is then either concluded or other information follows: a[<controller]: ac49x ch <ch> ibs <dtmf> <dir> <mode> <lev> <dur>Table 10.25 DTMF Tone RecognitionTrace Output Description<ch> Media channel<dtmf> Recognized DTMF tone in the stream or as per RFC2833<dir> Direction0Coming from BRI/analog1Coming from VoIP<mode> 0Tone has ended1Tone has been recognized<lev> Signal level in -dBm<dur> Tone durationpstn<type> <mt1> dad <num> oad <num> cc <value> cc <cc> id <id> c/c <ctrl>/<ch> cr <cr> Table 10.26 Internal Protocol Interface Trace Output Description<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 10.11.<num> DAD<num> = called party number, OAD<num> = calling party number.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10184iGATE 15.0. Revised: 2009.Output also appears when a call comes from the internal protocol interface and is assigned to a VoIP profile. Thecharacters 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 appearsas follows:<cc> Value for OAD field element:20 OAD network type provided40 OAD with sending complete80 OAD presentation restricted<id> Internal ident for the call leg.<ctrl> Controller used (counting starts with 0).<ch> Media channel used (counting starts with 1).<cr> Internal call reference /, followed by 0 or call reference of the VoIP leg.pstnrcv get_voipcfg <voip profile> compr <list>Table 10.27 Received from PSTN 1 Trace Output Description<voip profile> Defines the VoIP profile to be used.<list> Defines the compression algorithms offered.pstnrcv bchanind cr <cr> ch <chan> isdncr <icr>Table 10.28 Received from PSTN 2Trace Output Description<cr> Call reference.<chan> Media channel used for the internal protocol interface (DSS1).<icr> Call reference for the internal protocol interface (DSS1).Table 10.26 Internal Protocol Interface (continued)Trace Output Description
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10185iGATE 15.0. Revised: 2009.10.4.3.3 H.245 MESSAGESThe 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: h245<dir>(<tt>) cr <cr>Table 10.29 H.245 Messages Trace Output Description<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 10.30 Codec Used Trace Output Description<comp> List of compression codecs offered (see Table 10.13 >), the list of the peer's codecs ap-pears behind peer, and cfg shows which codecs are defined in the VoIP profile... OpenLogicalChannel cn=<cn> cpr=<comp> sessid=<sid> ctrl=<ip address>:<rtcp port>... OpenLogicalChannelAck cn=<cn> sessid=<sid> media=<ip address>:<rtp port>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10186iGATE 15.0. Revised: 2009.The trace output is as follows when the message type is not translated or is ignored:Table 10.31 Logical Channel Parameters Trace Output Description<cn> H.245 channel number per H.225 connection.<sid> Session ID.<comp> Codec used (see Table 10.13 >).<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 10.32 H.245 Parameters Trace Output Descriptionhmt The H.245 message type (multimedia system control message type), (Table 10.33 >).hmi The H.245 message ID (see Table 10.34 >, Table 10.35 >, Table 10.36 >, Table 10.37 >).Table 10.33 Multimedia System Control Message Types ID Message0 (Table 10.34 >) Request1 (Table 10.35 >)Response2 (Table 10.36 >)Command3 (Table 10.37 >) Indication
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10187iGATE 15.0. Revised: 2009.Depending on the system control message type, one of the following message IDs appear: Table 10.34 Message IDs for Request Message ID Message0 NonStandard1 MasterSlaveDetermination2 TerminalCapabilitySet3 OpenLogicalChannel4 CloseLogicalChannel5 RequestChannelClose6 MultiplexEntrySend7 RequestMultiplexEntry8 RequestMode9 RoundTripDelayRequest10 MaintenanceLoopRequest11 CommunicationModeRequest12 ConferenceRequest13 MultilinkRequest14 LogicalChannelRateRequestTable 10.35 Message IDs for Response Message ID Message0NonStandard1 MasterSlaveDeterminationAck2 MasterSlaveDeterminationReject3 TerminalCapabilitySetAck4 TerminalCapabilitySetReject5 OpenLogicalChannelAck6 OpenLogicalChannelReject
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10188iGATE 15.0. Revised: 2009. 7 CloseLogicalChannelAck8 RequestChannelCloseAck9 RequestChannelCloseReject10 MultiplexEntrySendAck11 MultiplexEntrySendReject12 RequestMultiplexEntryAck13 RequestMultiplexEntryReject14 RequestModeAck15 RequestModeReject16 RoundTripDelayResponse17 MaintenanceLoopAck18 MaintenanceLoopReject19 CommunicationModeResponse20 ConferenceResponse21 MultilinkResponse22 LogicalChannelRateAcknowledge23 LogicalChannelRateRejectTable 10.36 Message IDs for Command Message ID Message0 NonStandard1 MaintenanceLoopOffCommand2 SendTerminalCapabilitySet3 EncryptionCommand4 FlowControlCommand5 EndSessionCommandTable 10.35 Message IDs for Response Message (continued)ID Message
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10189iGATE 15.0. Revised: 2009.6MiscellaneousCommand7 CommunicationModeCommand8 ConferenceCommand9 h223MultiplexReconfiguration10 NewATMVCCommand11 MobileMultilinkReconfigurationCommandTable 10.37 Message IDs For Indication Message ID Message0 NonStandard1 FunctionNotUnderstood2 MasterSlaveDeterminationRelease 3 TerminalCapabilitySetRelease4 OpenLogicalChannelConfirm5 RequestChannelCloseRelease6 MultiplexEntrySendRelease7 RequestMultiplexEntryRelease8 RequestModeRelease9 MiscellaneousIndication10 JitterIndication11 h223SkewIndication12 NewATMVCIndication13 UserInput14 h2250MaximumSkewIndication15 McLocationIndication16 ConferenceIndicationTable 10.36 Message IDs for Command Message (continued)ID Message
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10190iGATE 15.0. Revised: 2009.10.4.3.4 RAS (REGISTRATION, ADMISSION, STATUS)As a general rule, the most important terminal and gatekeeper messages appear written out with the gatekeeper'sIP address (<ip addr>): 17 VendorIdentification18 FunctionNotSupported19 MultilinkIndication20 LogicalChannelRateRelease21 FlowControlIndication22 MobileMultilinkReconfigurationIndicationH225 GatekeeperRequest to <ip addr> (s 131)H225 GatekeeperConfirm <ip addr>H225 GatekeeperReject <ip addr> reason <reason>Table 10.38 RAS Trace Output Description<reason> Gatekeeper reject reason, see Table 10.42 >.H225 GkRegistration to <ip addr>H225 RegistrationConfirm <ip addr>H225 RegistrationReject <ip addr> reason <reason>Table 10.39 Gatekeeper 1 Trace Output Description<reason> Registration reject reason, see Table 10.43 >.Table 10.37 Message IDs For Indication Message (continued)ID Message
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10191iGATE 15.0. Revised: 2009.All other messages appear as follows: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>Table 10.40 Gatekeeper 2 Trace Output Description<reason> Admission reject reason, see Table 10.44 >.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>Table 10.41 Gatekeeper 3 Trace Output Description<code> Unknown gatekeeper message, see Table 10.45 >.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10192iGATE 15.0. Revised: 2009.Table 10.42 Gatekeeper Reject Reason ID Reject Reason0 resourceUnavailable1terminalExcluded2invalidRevision3 undefinedReason4 securityDenial5 genericDataReason6 neededFeatureNotSupportedTable 10.43 Registration Reject Reason ID Reject Reason0DiscoveryRequired1 InvalidRevision2 InvalidCallSignalAddress3 InvalidRASAddress4 DuplicateAlias5 InvalidTerminalType6 UndefinedReason7 TransportNotSupported8 TransportQOSNotSupported9 ResourceUnavailable10 InvalidAlias11 SecurityDenial12 RullRegistrationRequired
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10193iGATE 15.0. Revised: 2009.13 AdditiveRegistrationNotSupported14 InvalidTerminalAliases15 GenericDataReason16 NeededFeatureNotSupportedTable 10.44 Admission Reject Reason ID Reject Reason0 CalledPartyNotRegistered1InvalidPermission2 RequestDenied3 UndefinedReason4 CallerNotRegistered5 RouteCallToGatekeeper6 InvalidEndpointIdentifier7 ResourceUnavailable8 SecurityDenial9 QosControlNotSupported10 IncompleteAddress11 AliasesInconsistent12 RouteCallToSCN13 ExceedsCallCapacity14 CollectDestination15 CollectPIN16 GenericDataReason17 NeededFeatureNotSupportedTable 10.43 Registration Reject Reason (continued)ID Reject Reason
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10194iGATE 15.0. Revised: 2009.Table 10.45 Unknown Gatekeeper Messages ID Message0 GatekeeperRequest1 GatekeeperConfirm 2 GatekeeperReject 3 RegistrationRequest 4 RegistrationConfirm 5 RegistrationReject 6 UnregistrationRequest 7 UnregistrationConfirm 8 UnregistrationReject 9AdmissionRequest 10 AdmissionConfirm 11 AdmissionReject 12 BandwidthRequest 13 BandwidthConfirm 14 BandwidthReject 15 DisengageRequest 16 DisengageConfirm 17 DisengageReject 18 LocationRequest 19 LocationConfirm 20 LocationReject 21 InfoRequest 22 InfoRequestResponse 23 NonStandardMessage 24 UnknownMessageResponse 25 RequestInProgress
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10195iGATE 15.0. Revised: 2009.10.4.3.5 ENUM OUTPUTThis output is assigned to group i and occurs with Layer2 and Layer3 traces:10.4.3.6 EXAMPLESThe following examples are offline traces. You can generate them using the GATE Manager or FTP commands. Thefilename is trace.log. The following cases appear in the examples:Incoming H323 Call with FastStart > Outgoing H323 Call with FastStart >Fax Call > 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 10.46 ENUM Output Trace Output Description<cr> Call reference.<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 pattern> Displays the DNS response. 0 appears if the number was not found.Table 10.45 Unknown Gatekeeper Messages (continued)ID Message
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10196iGATE 15.0. Revised: 2009.Incoming H323 Call with FastStart [15:25:13.65] i[02]: h225accept from 172.16.0.200 s 4[15:25:13.75] y[02]: h225rcv tpkt msg 5 h225cr 8006 addr 172.16.0.200 pt 0[15:25:13.75] y[02]: h225 decode rc 0, q931 msg 5 (0), len 364[15:25:13.75] y[02]: h225rcv setup voipcfg addr 172.16.0.200 rc 0 <DF> compr EABG[15:25:13.75] y[02]: h225rcv faststart <A1B1E1G0>[15:25:13.75] y[02]: h225rcv setup oad 01 00 <111> <> dad 01 <123456> rad <> bc 038090a3 0101[15:25:13.75] y[02]: h225rcv setup h225cr 8006 FS:1(E,172.16.0.200,29000) TUNN:1 H245:0(0,0)[15:25:13.75] y[02]: h225rcv setup h225cr 8006 cr 7[15:25:13.75] i[02]: pstnsnd setup dad 123456 oad 1 cr 7 s 4[15:25:13.75] s[00]: 00 01 52 4c 08 02 00 08 05 04 03 80 90 a3 18 03 a1 83 87 6c 04 81 31 31 31 70 07 81 31 32 33 34 35 36 7d 02 91 81 [15:25:13.75] i[02]: pstnrcv connresp cr 7 acc 5 ch 1[15:25:13.75] x[02]: h225snd callproc typ d cr 7 pri 0[15:25:13.75] r[00]: 00 01 01 54 [15:25:13.75] r[00]: 02 01 4c 54 08 02 80 08 0d 18 03 a9 83 87 [15:25:13.75] s[00]: 02 01 01 4e [15:25:14.33] r[00]: 02 01 4e 54 08 02 80 08 01 [15:25:14.33] s[00]: 02 01 01 50 [15:25:14.33] i[02]: pstnrcv alert cr 7 cls ff[15:25:14.33] i[02]: rtp start cr 7 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 1[15:25:14.33] x[02]: h225snd callproc typ 1 cr 7 pri 8[15:25:14.34] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[15:25:14.38] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[15:25:14.38] a[02]: vp ch 0: in 0 out 74[15:25:15.57] r[00]: 02 01 50 54 08 02 80 08 07 29 05 06 03 18 0f 17 4c 06 01 81 31 37 33 31 [15:25:15.57] s[00]: 00 01 54 52 08 02 00 08 0f [15:25:15.57] i[02]: pstnrcv connresp cr 7 acc 10 ch 255[15:25:15.57] x[02]: h225snd callproc typ 7 cr 7 pri 0[15:25:15.58] r[00]: 00 01 01 56 [15:25:17.01] a[02]: vp rtcp 0: SR Rx pc 110 oc 1816 ji 158 rt -1 fl 2 cl 1[15:25:20.09] a[02]: vp rtcp 0: SR Tx pc 277 oc 5496 ji 164 rt 0 fl 0 cl 0[15:25:20.09] a[02]: vp ch 0: in 18166 out 20646[15:25:20.09] a[02]: vp rtcp 0: SR Rx pc 258 oc 4634 ji 208 rt -1 fl 0 cl 1[15:25:23.32] a[02]: vp rtcp 0: SR Tx pc 441 oc 8776 ji 176 rt 0 fl 0 cl 0[15:25:23.32] a[02]: vp ch 0: in 28966 out 32900[15:25:24.68] y[02]: h225rcv tpkt msg 5a h225cr 8006 addr 172.16.0.200 pt 800e7800[15:25:24.68] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[15:25:24.68] y[02]: h225rcv relack h225cr 8006 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:25:24.68] y[02]: h225rcv relack h225cr 8006 cau 0x10[15:25:24.68] i[02]: rtp hold cr 7 ch 1[15:25:24.68] s[00]: 00 01 56 52 08 02 00 08 45 08 02 80 90 [15:25:24.68] i[02]: h225 connection 4 terminated[15:25:24.69] r[00]: 00 01 01 58 [15:25:25.89] r[00]: 02 01 52 58 08 02 80 08 4d [15:25:25.89] s[00]: 00 01 58 54 08 02 00 08 5a [15:25:25.94] i[02]: pstnrcv terminate connection (3201) cr 7 cau 1 err 16 state 17 ch 1 rsid 1[15:25:25.94] i[02]: rtp stop cr 7 ch 1[15:25:25.94] r[00]: 00 01 01 5a [15:25:25.94] a[02]: vp ch 0: in 34096 out 38154[15:25:25.94] a[02]: vp stop ch=0
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10197iGATE 15.0. Revised: 2009.Outgoing H323 Call with FastStart[15:04:09.12] r[00]: 02 01 46 48 08 02 22 54 05 04 03 80 90 a3 18 03 a9 83 94 6c 06 01 81 31 31 31 31 70 04 81 33 32 31 7d 02 91 81 [15:04:09.12] s[00]: 02 01 01 48 [15:04:09.12] s[00]: 00 01 48 48 08 02 a2 54 0d 18 03 a9 83 94 [15:04:09.12] i[02]: pstnrcv setup dad DF:321 oad 1111 cc 0 id 15d006[15:04:09.12] i[02]: pstnrcv get_voipcfg <DF>[15:04:09.12] i[02]: h225connect to 172.16.0.200 cr 6[15:04:09.12] x[02]: h225snd setup dad 1 cr 6[15:04:09.12] r[00]: 00 01 01 4a [15:04:09.15] y[02]: h225rcv tpkt msg d h225cr 6 addr 172.16.0.200 pt 80412800[15:04:09.15] y[02]: h225 decode rc 0, q931 msg d (11), len 32[15:04:09.15] y[02]: h225rcv msg d (11) h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:09.50] y[02]: h225rcv tpkt msg 1 h225cr 6 addr 172.16.0.200 pt 80412800[15:04:09.50] y[02]: h225 decode rc 0, q931 msg 1 (3), len 121[15:04:09.50] y[02]: h225rcv faststart <E1>[15:04:09.50] y[02]: h225rcv alert h225cr 6 FS:1(E,172.16.0.200,29000) TUNN:1 H245:0(0,0)[15:04:09.50] i[02]: rtp start cr 6 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 1[15:04:09.50] s[00]: 00 01 4a 48 08 02 a2 54 01 1e 02 80 88 [15:04:09.50] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[15:04:09.50] r[00]: 00 01 01 4c [15:04:09.53] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[15:04:09.53] a[02]: vp ch 0: in 0 out 74[15:04:11.79] y[02]: h225rcv tpkt msg 7 h225cr 6 addr 172.16.0.200 pt 80412800[15:04:11.79] y[02]: h225 decode rc 0, q931 msg 7 (2), len 79[15:04:11.79] y[02]: h225rcv connect h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:11.79] i[02]: pstnsnd connect cr 6[15:04:11.79] s[00]: 00 01 4c 48 08 02 a2 54 07 [15:04:11.80] r[00]: 02 01 48 4e 08 02 22 54 0f [15:04:11.80] s[00]: 02 01 01 4a [15:04:12.50] a[02]: vp rtcp 0: SR Rx pc 21 oc 394 ji 201 rt -1 fl 0 cl 0[15:04:16.13] a[02]: vp rtcp 0: SR Tx pc 192 oc 3236 ji 196 rt 0 fl 0 cl 0[15:04:16.13] a[02]: vp ch 0: in 14612 out 13796[15:04:17.98] y[02]: h225rcv tpkt msg 5a h225cr 6 addr 172.16.0.200 pt 80412800[15:04:17.98] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[15:04:17.98] y[02]: h225rcv relack h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:17.98] y[02]: h225rcv relack h225cr 6 cau 0x10[15:04:17.98] i[02]: rtp hold cr 6 ch 1[15:04:17.98] s[00]: 00 01 4e 4a 08 02 a2 54 45 08 02 80 90 [15:04:17.98] i[02]: h225 connection 4 terminated[15:04:17.99] r[00]: 00 01 01 50 [15:04:18.04] r[00]: 02 01 4a 50 08 02 22 54 4d 08 02 84 90 [15:04:18.04] s[00]: 00 01 50 4c 08 02 a2 54 5a [15:04:18.06] i[02]: pstnrcv terminate connection (3201) cr 6 cau 90 err 16 state 17 ch 1 rsid 1[15:04:18.06] i[02]: rtp stop cr 6 ch 1[15:04:18.06] r[00]: 00 01 01 52 [15:04:18.06] a[02]: vp ch 0: in 21288 out 20708[15:04:18.06] a[02]: vp stop ch=0
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10198iGATE 15.0. Revised: 2009.Fax Call[16:00:40.44] i[02]: h225accept from 172.20.0.200 s 4[16:00:40.49] y[02]: h225rcv tpkt msg 5 h225cr 8007 addr 172.20.0.200 pt 0[16:00:40.49] y[02]: h225 decode rc 0, q931 msg 5 (0), len 251[16:00:40.49] y[02]: h225rcv setup voipcfg addr 172.20.0.200 rc 0 <DF> compr EABG[16:00:40.49] y[02]: h225rcv faststart <E0G0>[16:00:40.49] y[02]: h225rcv setup oad 00 00 <> <> dad 01 <123456> rad <> bc 038090a3 0101[16:00:40.49] y[02]: h225rcv setup h225cr 8007 FS:1(E,172.20.0.200,29000) TUNN:1 H245:0(0,0)[16:00:40.49] y[02]: h225rcv setup h225cr 8007 cr 14[16:00:40.49] i[02]: pstnsnd setup dad 123456 oad cr 14 s 4[16:00:40.49] s[00]: 00 01 5a 54 08 02 00 09 05 04 03 80 90 a3 18 03 a1 83 88 70 07 81 31 32 33 34 35 36 7d 02 91 81 [16:00:40.49] i[02]: pstnrcv connresp cr 14 acc 5 ch 1[16:00:40.49] x[02]: h225snd callproc typ d cr 14 pri 0[16:00:40.50] r[00]: 02 01 54 5c 08 02 80 09 0d 18 03 a9 83 88 [16:00:40.67] r[00]: 02 01 56 5c 08 02 80 09 01 [16:00:40.67] i[02]: pstnrcv alert cr 14 cls ff[16:00:40.67] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 2[16:00:40.67] x[02]: h225snd callproc typ 1 cr 14 pri 8[16:00:40.70] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[16:00:40.74] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[16:00:40.74] a[02]: vp ch 0: in 0 out 74[16:00:40.90] r[00]: 02 01 58 5c 08 02 80 09 07 29 05 06 03 18 0f 3b 4c 08 01 81 31 32 33 34 35 36[16:00:40.90] s[00]: 00 01 5c 5a 08 02 00 09 0f [16:00:40.90] i[02]: pstnrcv connresp cr 14 acc 10 ch 255[16:00:40.90] x[02]: h225snd callproc typ 7 cr 14 pri 0[16:00:41.98] a[02]: vp rtcp 0: SR Rx pc 134 oc 1340 ji 195 rt -1 fl 0 cl 0[16:00:43.29] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.29] y[02]: h225 decode rc 0, q931 msg 62 (6), len 123[16:00:43.29] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.29] i[02]: h245rcv(1) cr 14 TerminalCapabilitySet peer=<EG> cfg=<EABG>[16:00:43.29] i[02]: h245snd(1) cr 14 TerminalCapabilitySetAck[16:00:43.29] i[02]: h245snd(1) cr 14 TerminalCapabilitySet <EABG>[16:00:43.51] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.51] y[02]: h225 decode rc 0, q931 msg 62 (6), len 63[16:00:43.51] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.51] i[02]: h245rcv(1) cr 14 TerminalCapabilitySetAck[16:00:43.72] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.72] y[02]: h225 decode rc 0, q931 msg 62 (6), len 74[16:00:43.72] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.72] i[02]: h245rcv(1) cr 14 RequestMode t38=1[16:00:43.72] i[02]: h245snd(1) cr 14 RequestModeAck[16:00:43.73] i[02]: h245snd(1) cr 14 CloseLogicalChannel cn=1[16:00:43.73] i[02]: h245snd(1) cr 14 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.100:29001[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 68[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 CloseLogicalChannel cn=1 (1)[16:00:43.73] i[02]: h245snd(1) cr 14 CloseLogicalChannelAck cn=1[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 92[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.200:29001[16:00:43.73] i[02]: h245snd(1) cr 14 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.100:29000[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 64[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 CloseLogicalChannelAck cn=1[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 83[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.200:29000
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10199iGATE 15.0. Revised: 2009.10.4.4 REMOTE OUTPUTThis 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 limitedto 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.73] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 3 fx 0 cp G txm 2[16:00:43.73] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 3 fx 1 cp G txm 2[16:00:43.74] a[02]: vp start2 ch=0 remote=ac1000c8:29000[16:00:43.74] a[02]: vp start(401) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[16:00:47.70] a[02]: vp rtcp 0: SR Tx pc 13 oc 352 ji 132 rt 0 fl 0 cl 0[16:00:53.63] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:00:59.14] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:02.12] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:07.16] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:11.82] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:18.06] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:21.15] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:26.10] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:28.89] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:33.14] y[02]: h225rcv tpkt msg 5a h225cr 8007 addr 172.20.0.200 pt 80410800[16:01:33.14] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[16:01:33.14] y[02]: h225rcv relack h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:01:33.14] y[02]: h225rcv relack h225cr 8007 cau 0x10[16:01:33.14] i[02]: rtp hold cr 14 ch 1[16:01:33.15] s[00]: 00 01 5e 5a 08 02 00 09 45 08 02 80 90 [16:01:33.15] i[02]: h225 connection 4 terminated[16:01:33.19] r[00]: 02 01 5a 60 08 02 80 09 4d [16:01:33.19] s[00]: 00 01 60 5c 08 02 00 09 5a [16:01:33.19] i[02]: pstnrcv terminate connection (3201) cr 14 cau 1 err 16 state 17 ch 1 rsid 1[16:01:33.19] i[02]: rtp stop cr 14 ch 1[16:01:33.23] a[02]: vp ch 0: in 85542 out 4346[16:01:33.23] a[02]: vp stop ch=0g[99]:moip: accept rc=2 ipad=<ip address> port=<port>Table 10.47 Remote Output Trace Output Description<ip address> Remote system’s IP address with GATE Manager.<port> Origination port for the GATE Manager connection.g[99]:moip: <direction> <length>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10200iGATE 15.0. Revised: 2009.All other trace output appears in detail mode in ASCII and are also translated.10.4.5 SMTP TRACE OUTPUTThis trace option provides output for communication with the mail server that occurs when status information orfiles are sent, or in the other direction, which e-mails are received and converted to SMS or USSD.To activate this option, activate the section Mail in the GATE Manager. You can choose the depth of the traceoutput: 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 InformationGlobal message output: Detailed message output: Table 10.48 Remote Output Trace Output Description<direction> recv Packets received from the remote systemsend Packets sent to the remote systemwrite Output for communication with the internal remote interfaceread Output for communication from the internal remote interface<length> Data length in bytes.m[99]:mail: sendmail (<length>)Table 10.49 SMTP Output: Sending Files or Status Info Trace Output Description<length> Data length in bytes.m[99]:mail: sendmail: <Faccount> <ip address> <Taccount> <domain> <subject> <content>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10201iGATE 15.0. Revised: 2009.All other trace output appears in detail mode in ASCII and are also translated.Receiving E-Mail Messages and Sending Them as SMS or USSDThe following output displays communication of an incoming SMTP connection:The following output displays which packets are sent to the SMTP peer: Table 10.50 SMTP Output: Sending Files or Status Info Trace Output Description<Faccount> Sender’s e-mail account (cdr, alarm, file, etc.).<ip address> SMTP server’s IP address.<Taccount> Recipient’s e-mail account.<domain> Recipient’s domain.<subject> Content of the subject field; serial number of the sender system.<content> Content of the message’s body.m[99]:mail: accept: ipad=<ip address> port=<port>Table 10.51 SMTP Output: Receiving E-Mail and Sending as SMS or USSD Trace Output Description<ip address> The SMTP peer system’s IP address.<port> The SMTP peer system’s origination port.m[99]:mail: mysend <<content>>Table 10.52 SMTP Output: Receiving E-Mail and Sending as SMS or USSD Trace Output Description<content> Content of the transmitted packet.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10202iGATE 15.0. Revised: 2009.All other trace output appears in detail mode in ASCII and are also translated.The following output displays which packets are received from the SMTP peer: All other trace output appears in detail mode in ASCII and are also translated.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: 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 >.m[99]:mail: recv (<length>)Table 10.53 SMTP Output: Receiving E-Mail and Sending as SMS or USSD Trace Output Description<length> Data length in bytes.m[99]:mail: terminate_sessionm[99]:mail: newMail2Host r=<Taccount> f=<Faccount> s=<subject> d=<content>Table 10.54 SMTP Output: Receiving E-Mail and Sending as SMS or USSD Trace Output Description<Faccount> One entry from the sender’s To field.<Taccount> Content of the From field.<subject> Content of the subject field; usually not used.<content> Content of the message’s body; is sent as SMS or USSD.m[99]:mail: rcvmail <Faccount> -> <Taccount>, done
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10203iGATE 15.0. Revised: 2009.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 SendingFiles or Status Information >. Receiving SMS or USSD and Sending as E-MailThe following output shows the internal format when an SMS or USSD message is sent to the mail module. Thisoutput 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 >.10.4.6 NUMBER PORTABILITY TRACE OUTPUTThis trace option provides output for the communication with the iMNP database. To activate this option, activatethe 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: m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed, will retry (<num>)Table 10.55 SMTP Output: Transmission Error Trace Output Description<num> Current number of retries.m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed <num> timesm[99]:mail: DATA_IND (<length>)n[99]:np: connecting to <ip addr>Table 10.56 Number Portability Output: Connection with iMNP Trace Output Description<ip address> The iMNP system’s IP address.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10204iGATE 15.0. Revised: 2009.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 call’s routing: 10.4.7 DTMF TONE TRACE OUTPUTOutput 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 ofthe virtual DTMF controller:The following output shows incoming call setup to the DTMF module: n[99]:np: connect to <ip addr> okn[99]:np: connect to <ip addr> failedn[99]:np: recv <>n[99]:np: recv <N<num>>Table 10.57 Number Portability Output: Response Trace Output Description<num> Ported or unported number provided by the database.d[<ctrl>]: dtmf: msg <call state>, unknown id <id>, from 14Table 10.58 DTMF Output: Incoming Call Setup Trace Output Description<ctrl> The virual controller’s running number.<call state> 3101 Incoming setup3201 Disconnect request<id> Call identification number.
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10205iGATE 15.0. Revised: 2009.The following output shows transmitted signaling messages depending on the call state: The following output shows that the media channel has been designated for DTMF tone recognition: d[<ctrl>]: dtmf <message type> <id> <call state> 0Table 10.59 DTMF Output: Signaling Messages Trace Output Description<message type> Send_d_connect For setup acknowledge and connect.send_alert_ind For alert.send_disconnect For disconnect<id> Call identification number.<call state> 3110 Incoming setup3102 Disconnect request3804 Alert3202 Disconnect confirmationd[<ctrl>]: dtmf send_alloc <b_chan id_unset> <ctrl>/<b chan>Table 10.60 DTMF Output: Media Channel Designation Trace Output Description<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>
SYSTEM MAINTENANCE AND SOFTWARE UPDATECHAPTER 10206iGATE 15.0. Revised: 2009.The following output shows the output for negotiated DTMF tones: Table 10.61 DTMF Output: Media Channel Designation Trace Output Description<msg> 502 Media channel confirmation102 Connect confirmation602 Media channel free confirmationd[<ctrl>]: dtmf send_info_ind <id> <<dtmf tone>>
FEATURE PACKAGESCHAPTER 11207iGATE 15.0. Revised: 2009.11 FEATURE PACKAGESThe iGATE feature packages are modular expansion applications that provide services in addition to those offeredwith the standard software. Feature packages can be activated separately or in combination with one another, sothat you can design your system according to your own needs.The following feature packages are available:Dial-In/Callback Services (cf. Chapter 11.2 on page 208 >)Least Cost Routing (cf. Chapter 11.3 on page 213 >)Online Traffic Monitor (cf. Chapter 11.4 on page 219 >)SMS Gateway (cf. Chapter 11.5 on page 228 >)Ported Number Screening (cf. Chapter 11.6 on page 232 >)11.1 ACTIVATING THE LICENSEEach feature package requires a license. Once you have ordered a feature package, you can activate the license:The /boot/ directory of each system contains a file called license.key, which contains information on the system’sID, the included components, which feature packages are active and the license number:Example: You will receive a new license.key file any time you order a new license package. Simply save the new file, over-writing the old file, and restart the system. [IDENTIFICATION]SYSTEM: TELES.iGATESERNO: VT810011AUTOR: create Wed Sep 09 15:01:09 2006[COMPONENTS]...CARD99:11 d1 S0 PB900034...[FEATURES]PRI:MaxGSM:MaxIP:MaxVoIP:MaxSIM manager: OnDDI and call back: Offleast cost routing: Onstatistics and CDR: OnSMS gateway: Onported number screening: Offroaming: Off[SIGNATURE]00000000000license0number00000000000Deleting or making changes in the license.key file will delete any feature package licenses, causing the system to revert to the standard configuration! ii
FEATURE PACKAGESCHAPTER 11208iGATE 15.0. Revised: 2009.11.2 DLA/CALLBACK SERVER FUNCTIONALITYThis package contains money-saving features that expand the functionality of your iGATE to include callback ca-pability and DTMF services. It is particularly useful for companies with employees who travel often, because it elim-inates expensive roaming fees:11.2.1 CALL CONNECTOR AND CALLBACK SERVERDepending on your iGATE, various intelligent solutions as a call server are possible. The most important scenariosand 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, afterwhich DTMF transmission will automatically end.If the callback call is set up from the mobile network, the SIM must be available 24 hours a day. We recommendthat you reserve a SIM for this service. Otherwise, another call could block the call initiating callback, which limitsthe effectiveness of the service.Activating DTMF Tone RecognitionThe iGATE can recognize DTMF tones and initiate calls with these tones. In the pabx.cfg, enter a virtual DTMF con-troller, as described in Table 5.13 >. The corresponding Subscriber entry contains the options:TRANSPARENT ROUTER CHMAX[5]The 5 refers to the maximum number of simultaneous channels used for DTMF recognition.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 subscriber’s connection time is generated in the failed.log file.ii
FEATURE PACKAGESCHAPTER 11209iGATE 15.0. Revised: 2009.Example: The iGATE must be restarted to activate this configuration.11.2.1.1 SPECIAL ANNOUNCEMENTAn announcement can be played immediately after the connection has been established. The announcement canbe defined in the virtual DTMF controller’s 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> refersto 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 5 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:11.2.1.2 DLA WITH DTMFThe user dials a number in the system that is connected with the DTMF platform. She then enters the number withwhich she would like to be connected.Make the following entries in the route.cfg to connect a call directly:MapAll<number>=<DTMFport>DTMFMapAllDLA=<port> Example: In the following example, the call from the number 123 is connected to the DTMF platform andthe call that comes in as DTMF tones is directed to port 9: 11.2.1.3 DLA WITH FIXED DESTINATION NUMBERThe user dials a number in the system that is connected directly with a fixed external number (e.g. internationalsubsidiary number). Make the following entry in the route.cfg:...Controller06 = 41 DTMF...Subscriber06 = TRANSPARENT ROUTER CHMAX[5]...The file’s sound format must be PCM!Subscriber06 = TRANSPARENT ROUTER DTMF[30,/boot/DTMF.711] CHMAX[5]MapAll123=41DTMFMapAllDLA=9ii
FEATURE PACKAGESCHAPTER 11210iGATE 15.0. Revised: 2009.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 port 9.11.2.1.4 CALLBACK WITH DTMF AND OAD AS CALLBACK NUMBERThe 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 usingDTMF 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 party’s number:MapAllDTMF=<DTMFport>DTMFMapAllDLA=<port>MapAll<number>=CALLBMapAllCB=<port>Example: In this example, the call with the number 123 is connected with the OAD and the number thatcomes in as DTMF is directed to port 9:11.2.1.5 CALLBACK WITH DTMF AND PRE-CONFIGURED CALLBACK NUMBERThe user calls a predefined number that is mapped to a defined callback number. An alerting occurs. The userhangs up and is called back at a fixed number. If the parameter MapCallbackAlert=<sec> is configured, the iGATEwill release the trigger call. 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:MapAll123456=9004311111Callback is not possible for VoIP calls.MapAllDTMF=41DTMFMapAllDLA=9MapAll123=CALLBMapAllCB=9MapCallbackAlert=3Callback is not possible for VoIP calls.iiii
FEATURE PACKAGESCHAPTER 11211iGATE 15.0. Revised: 2009.MapAllDTMF=<DTMFport>DTMFMapAllDLA=<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 port 9: 11.2.1.6 CALLBACK TO OAD AND FIXED SECOND LEG The user calls a predefined number in the system. An alerting occurs. The user hangs up and is called back basedon her OAD. After the user accepts the call, she is connected to a fixed, preconfigured number (e.g. operator orcorporate central office.Make the following entries in route.cfg:MapAllDTMF=<port><num>MapAll<num>=CALLBMapAllCB=<port>Example: In the following example, the caller dials 123456 and her OAD is called back through port 9. Sheis then connected with the operator’s number 0 through port 10.11.2.1.7 DLA WITH DTMF AND PIN FOR FIRST LEG AND CALLBACK FOR SECOND LEGThe user dials a number in the system that is connected to the DTMF platform. He then enters a predefined PINthat 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:MapAllDTMF=<DTMFport>DTMFMapAll<num>=<DTMFport>DTMF VOICEMapAllDLA<num>=CALL<num> VOICEMapAllDLA=<port> VOICEExample: 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 port 9 using DTMFtones:MapAllDTMF=41DTMFMAPAllDLA=9MapAll123=CALL903012345Callback is not possible for VoIP calls.MapAllDTMF=100MAPAll123456=CALLBMapAllCB=9ii
FEATURE PACKAGESCHAPTER 11212iGATE 15.0. Revised: 2009.11.2.1.8 USING A PIN IN FRONT OF THE CALL NUMBERTo prevent abuse, the following entry can be made to configure a PIN in front of the actual call number:MapAllDLA=$PINMapAllPIN<pin>=<port>Example: In the following example, the DTMF tones are analyzed, whereby the first 4 (1111) correspondswith the PIN. The call to subscriber B is initiated when the PIN has been entered correctly. Allother DTMF tones are directed to port 9: 11.2.1.9 CALLBACK VIA SMSIf your TELES.System has an integrated iGATE 4 GSM Board, callback calls can be initiated via SMS. The callbackwill be sent to the mobile telephone that initiated the SMS. Once this connection has been set up, the second legis set up to the number sent in the SMS. This connection can be set up via GSM, ISDN or VoIP. This results in cheaper calls, for example in the case of in-ternational connections. The SMS must begin with the keyword CAL#, followed by the called number. The following mapping entries must appear in the pabx.cfg for the mobile phone requesting callback:MapAllCB<country><prefix>=<port> VOICEMapAllDLA=$placeMapAllplace<num>=<port><num>Restrict<port>=@FILE:<name> 05Example: In the following example, the SMS is sent from a mobile phone with the prefix 01555 to a spe-cific SIM (phone number) in the TELES.System. This SIM must be available 24 hours a day in theTELES.System and we recommend that it is reserved for this service. The callback call goesthrough a GSM port with LAIN 26212. After the first leg connection has been set up, the callto the second number, with the prefix 01556, is connected using the SIM with LAIN 26211.The placeholder $place causes a new search through the routing table, which means that dif-ferent prefixes can be used for different ports (PRI, GSM, VoIP). In the example, all calls to theUSA go through the public ISDN line:MapAllDTMF=41DTMFMAPAll123456=41DTMF VOICEMapAllDLA123=CALL9004930123456 VOICEMapAllDLA=9 VOICEThe user must enter a # following the PIN. Otherwise the callback to the predefined number will not occur.MapAllDLA=$PINMapAllPIN1111=9ii
FEATURE PACKAGESCHAPTER 11213iGATE 15.0. Revised: 2009.The following SMS text means that the second leg goes to the number 015561111111 via port 26211: 11.3 LEAST COST ROUTINGiGATEs are connected between the customer’s private branch exchange (PBX) and the public telephone network(ISDN) and/or VoIP. The customer saves connection charges and can effortlessly and automatically connect to thecorporate network as needed using one of six routing methods:Carrier selectionDedicated linesDirect line access with subaddressingDirect line access with DTMFCallback with subaddressingCallback with DTMFThis manual contains information only on carrier selection. If you would like to configure any other variation, pleasecontact TELES or refer to the TELES Infrastructure Systems Manual Version 4.5, Chapter 3.Calls are routed transparently for the PBX and its users. iGATEs can generate charges and route calls using alter-nate settings in case of network failures. The provider can access the system via ISDN for routine maintenance andmonitoring.The following additional services are supported by this feature package:Generation of chargesTime-controlled configurationAlternative routing11.3.1 CARRIER SELECTIONCarrier selection is currently one of the most commonly used routing methods supported by the iGATE. In theiGATE, this routing process also includes direct calls into the mobile network or through a VoIP network. Thatmeans the system is a full-fledged second generation LCR. 11.3.1.1 ROUTING ENTRIESUse the MapAll command to route calls using Carrier Selection. MapAllCB491555=2621201555 VOICEMapAllDLA=$placeMapAllplace01556=2621101556MapAllplace001=9001Restrict26212=@FILE:SMS.log 05CAL#015561111111
FEATURE PACKAGESCHAPTER 11214iGATE 15.0. Revised: 2009.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 numberrequired to reach the provider’s 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 profilenames iG1 and iG2 in the routing entries refer to different VoIP carriers. Calls to the mobile network (01555 and01556) are routed directly through SIM cards for the corresponding mobile carriers (LAIN 26212 and 26213). Allother national long distance and local calls are routed through an alternative carrier (01019). All calls from thePSTN to the PBX are put through transparently.Example:11.3.2 ALTERNATIVE ROUTING SETTINGSAlternative routing refers to the ability to establish connections using a different (alternative) network in case ofprovider failure (e.g. all mobile controllers are in use). Alternative routing ensures uninterrupted operation of theattached PBX. In such cases, connections are often made via the public network using the Redirect command: MapAll<num>=<port><num>Redirect3<port><num>=<placeholder>MapAll<placeholder>=<alt port><num>MapAll001=40iG1:001MapAll0044=40iG2:0044...MapAll01555=2621201555MapAll01556=2621301556...MapAll01=90101901MapAll02=90101902...MapAll09=90101909MapAll1=9010191MapAll2=9010192...MapAll9=9010199Restrict9=10Be sure to enter phone numbers in the routing file in ascending order.ii
FEATURE PACKAGESCHAPTER 11215iGATE 15.0. Revised: 2009.Example:11.3.3 CHARGE MODELSiGATEs can either generate charge information or transmit received charges from the public or corporate networksto the attached PBX. Charge simulation is achieved using variables, which ensure a great degree of flexibility forthe 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 currencymeans that the charge information is sent as a currency amount (e.g. EUR 3.45). The charge impulse generationoptions can be set for each mapping by adding charge-specific arguments to the MapAll commands as shown be-low. The use of each variable is explained in Table 11.1 >.MapAllsrc=dst mode time start/wait andMapCallBackOutprovsrc=dst mode time start/wait.MapAll01555=2621201555Redirect32621201555=AMapAllA=901555Table 11.1 Charge Variables Variable Purposetime 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 interval.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 seconds. 255 deactivates the charge pulse. In this case, the time variable is ignored.
FEATURE PACKAGESCHAPTER 11216iGATE 15.0. Revised: 2009.Any external charges can be added to the generated charges by adding 128 to the start value. (The value rangefor the initial unit level is still set from 0 to 127). The maximum supported number of units per connection is 32767units.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 precisionin 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 requiringaccuracy to the third decimal place or for fractions such as tenths of a cent. This allows for greater flexibility inthe transmission of charges to terminal devices. In order to make use of this option, connected devices mustsupport “AOC-D Currency”. In the current version, this option is only available for the DSS1 protocol.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 inthe 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:Example: In the following 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 byretroactive 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 217 >.11.3.4 GENERATING CHARGES WITH THE IGATETo generate charges for the attached PBX, add the charge variables described in Table 11.1 > to the MapAll com-mands according to the necessities of the corporate network environment.Example 1 In the following mapping example, time=1.65, start=131, wait=0. Three initial tariff units (131-128) are transmitted upon connection and a new unit is generated every 1.65 seconds and trans-mitted the next full second. Charges received from the public network for the connection to thecorporate network dial-in node are added and transmitted (because 128 has been added to thestart variable’s value).Example 2 Upon connection establishment, 3 initial tariff units (131-128) are transmitted. Then a 10-seconddelay (wait=10) elapses before charge impulses are generated according to the time variable (anew unit is generated every 1.65 seconds and transmitted the next full second). Charges received...MapAll1=91 1 128/255*12......MapAll0172=9123450172 1.65 131/0...
FEATURE PACKAGESCHAPTER 11217iGATE 15.0. Revised: 2009.from the public network for the connection to the corporate network dial-in node are added andtransmitted (because 128 has been added to the start variable’s value).New charge models can be implemented by taking advantage of the multiplication factor in conjunction with thetime and start/wait variables.Retroactive charge generation after initial toll-free periodExample: The charge generation process has been expanded to allow for the implementation of this newcharge model. In this scenario, an initial period is free of charge, but after this period charges arecalculated for the entire call. For example: the first minute is free, but as soon as the secondminute 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 remain-ing value represents the number of units charged with each time interval. The following config-uration generates one unit (129-128) per minute (time=60 seconds) retroactively after the firstminute (wait=60 sec.):“Price per minute”A price per minute charge model can be implemented as of version 5.01 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 ofa cent) to each charge unit.This model does not always guarantee whole second accuracy (depending on the rates), but it is significantly moreprecise than the standard charge generation method.Example 1 If the attached PBX supports Advice of Charges as Currency, include the following line in theiGATE’s pabx.cfg:Example 2 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 neednot be present. The configuration entries must make use of the multiplication factor for a single...MapAll0172=9123450172 1.65 131/10......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 NTS2M DSS1 CRC4 UNIT:€ VALUE:0.001...ii
FEATURE PACKAGESCHAPTER 11218iGATE 15.0. Revised: 2009.unit as shown below:Example 3 If the minute price does not allow generated charges to “fit” evenly into a second (such as 20cents 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):Example 4 The “points” method allows for a more precise calculation of smaller intervals. The price per minute can also be explicitly specified in each routing entry by setting the multipli-cation factor to 255, to signalize to the system that a minute price is being used instead of theinterval usually specified with the time variable. The attached PBX must support Advice of Charg-es as Currency, and the appropriate settings must be made in the iGATE’s pabx.cfg as describedon page 217 >. The examples below show sample entries with rates of 18 and 9 cents perminute:andExample 5 If greater precision is desired (¹⁄1000 of a currency unit – $0.001 or ¹⁄10 of a cent), use settingssuch as the following:and...MapAll902=90103002 1.00 0/0*4 ; each second costs €0.004 (€0.24 / minute)MapAll909=90108809 1.00 0/0*5 ; each second costs €0.005 (€0.30 / minute)......MapAll902=90101302 3.00 0/0*10 ; 3 seconds cost €0.01 (€0.20 / minute)MapAll909=90105009 2.00 0/0*3 ; 2 seconds cost €0.003 (€0.09 / minute)......MapAll902=90101302 0.18 0/0*255 ; €0.18 / minute MapAll909=90105009 0.09 0/0*255 ; €0.09 / minute ......Controller01=10 NTS2M DSS1 CRC4 UNIT:€ VALUE:0.010......MapAll902=90101302 1.80 0/0*255 ; €0.18 / minute MapAll909=90105009 0.90 0/0*255 ; €0.09 / minute ......Controller01=10 NTS2M DSS1 CRC4 UNIT:€ VALUE:0.001...
FEATURE PACKAGESCHAPTER 11219iGATE 15.0. Revised: 2009.11.4 ONLINE TRAFFIC MONITORThe Online Traffic Monitor allows you to collect and monitor statistics and call detail records (CDRs). The followingfunctions are possible with this feature package:ASR calculationGeneration of CDRsGeneration of online CDRs using e-mail11.4.1 ASR CALCULATION AND RESETTING STATISTIC VALUES AND COUNTERSWhen these functions are configured in the pabx.cfg file, the following statistic values are calculated for the entiresystem at a defined time and are copied into a file in the following order:Day and time of entrySystem nameNumber of connected calls followed by the number of total calls in parenthesesNumber of minutes termintatedASR1: ratio of total calls to connected calls disconnected by the A partyASR(ext): external ASR for the traffic sourceASR(int): internal ASR for the iGATEACD: average call durationExample: The following example shows how the statistics appear in the file into which they are copied: Set the time using the following syntax: <hh:mm>. If ?? appears instead of a specified hour (e.g. ??:mm), theASR is written into the asr.log file once every hour. You can set <day> to apply for days of the week or for one specific day of the month as follows:Use a bitmask to set the weekdays on which the configuration applies here. The daymap appears in the followingorder: HoSaFrThWeTuMoSu. For example, enter 00000001 if the configuration is to apply every Sunday. To set the configuration to apply on one specific day every month, enter the day of the month followed by a fullstop. For example, enter 15. if the configuration is to apply on the 15th of every month.If the configuration is to apply every day, do not set <day>.26.10.04-00:00:00,iGATE810000: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% - ASR(ext): 65.12% - ASR(int): 65.30% - ACD: 144.63s Do not configure both StatisticTimeReset and StatisticTime or StatisticTimeReset and StatisticCounter together. ii
FEATURE PACKAGESCHAPTER 11220iGATE 15.0. Revised: 2009.11.4.1.1 SAVING AND SENDING STATISTICSThe statistics are copied into a specified file. This information can also be sent to an e-mail or SMS recipient. Thefollowing syntax must be used: StatisticTime=/data/asr.log <hh:mm> <day>StatisticTime=/data/asr.log <hh:mm> <day> @<email address> StatisticTime=/data/asr.log <hh:mm> <day> @SMS<mobile number>Example: In the following example, the system’s statistic values are saved every Wednesday into the fileasr.log and sent to an e-mail account. Example: In the following example, the system’s statistic values are saved at midnight on the first of everymonth into the file asr.log and sent to an SMS recipient. 11.4.1.2 SAVING STATISTICS AND RESETTING STATISTIC COUNTERSThe statistics are copied into a specified file and the counters (A-F) are reset. The following syntax must be used: StatisticTimeReset=/data/asr.log <hh:mm> <day> Example: In the following example, statistics will be saved every hour on the hour of every day and thestatistic counters will be reset to 0.Example: In the following example, the system’s statistic values are saved at noon on the 15th of everymonth into the file asr.log. StatisticTime=/data/asr.log 00:00 00001000 @info@teles.deStatisticTime=/data/asr.log 00:00 01. @SMS01234567890Do not configure both StatisticTimeReset and StatisticTime together.StatisticTimeReset=/data/asr.log ??:00StatisticTimeReset=/data/asr.log 12:00 15.Do not configure both StatisticTimeReset and StatisticTime or StatisticTimeReset and StatisticCounter together. iiii
FEATURE PACKAGESCHAPTER 11221iGATE 15.0. Revised: 2009.11.4.1.3 RESETTING STATISTIC COUNTERSThe following setting in the pabx.cfg resets the statistic counters and unblocks the controller group. The followingsyntax must be used: ResetCounter=<LAIN> <hh:mm> <day> Up to five entries for as many groups and/or times are possible. The setting <LAIN> refers to a group of mobilecontrollers. Bear in mind that StatisticTimeReset must be inactive to avoid repetition.Example: In the following example the counters will reset for LAIN group 26211 every day at midnight, forthe group 26212 only once on the first day of the month, and for 26213 each Saturday at8:00pm:11.4.2 GENERATING AND RETRIEVING CDRSWith the Log and failedlog commands, you save CDRs and unconnected calls in the iGATE. For these parameters (Log and failedlog), a folder and file name must always be specified after the equalsign. The function is not active (no data is recorded) until a file name is specified. Example:ResetCounter = 26211 00:00 11111111ResetCounter = 26212 00:00 01.ResetCounter = 26213 20:00 01000000Do not configure both StatisticTimeReset and StatisticCounter together. Log=/data/cdr.log failedlog=/data/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.iiii
FEATURE PACKAGESCHAPTER 11222iGATE 15.0. Revised: 2009.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 listedbelow:0101 ISDN-telephony 3.1 kHz0102 analog telephony0103 ISDN-telephony 7 kHz0200 Fax group 20202 Fax group 30203 Data via modem0400 Telefax group 40500 SMS or BTX (64 kbps)0700 Data transfer 64 kbps07… Bit rate adaptation1001 Video telephone – audio 3.1 kHz1002 Video telephone – audio 7 kHz1003 Video telephone – videoFor detailed information on how to automatically divide the files (e.g. on a daily basis), please refer to theChapter 5.2.1.2 >.11.4.2.1 CALL LOGThe following entry in the pabx.cfg configuration file activates the capability to generate CDRs in the iGATE:Log=/data/cdr.logThe cdr.log file is stored in the data directory. New entries are always added to the end of the file. The file is openonly during editing. Each line represents an outgoing call with the following information separated by commas:Table 11.2 Call Log Entries Column Description0Version1Start time (format DD.MM.YY-hh.mm.ss)2End time (format DD.MM.YY-hh.mm.ss)3Source. The following format applies: [node number:automatically set internal channel number]4Destination. The following format applies: [node number:automatically set internal chan-nel number]5IMSI
FEATURE PACKAGESCHAPTER 11223iGATE 15.0. Revised: 2009.Sample Log FileThe example below shows a sample log file: Differentiating Between Ports in the Same Trunk GroupTo differentiate between ports with the same number in the CDRs, a specific node number must be defined. Youcan expand the subscriber configuration line with the keyword NODE[<no.>] for this purpose. <no.> can be astring of between 1 and 15 characters:Subscriber<xx>=... NODE[<num>]Example:In the above formula, <num> consists of a four-digit number that is included in the CDR. 6IP logging signaling: RTP7Audio codec used8Frame size9Service indicator (cf. Chapter 11.4.2 on page 221 >)10 Call duration11 Cause values12 Charge from the public line (in units)13 Charge generated from the system (in units)14 Cell ID15 RSSIV1,25.11.09-10:16:20,25.11.09-10:16:27,[0000:01]9,[0006:01]111,123456789123451,,,,0102,7,1f,0,,3663,10V1,25.11.09-10:35:16,25.11.09-10:35:26,[0000:01]9,[0004:01]111,123456789123452,,,,0102,10,1f,0,3,38922,14V1,25.11.09-10:38:30,25.11.09-10:38:41,[0000:01]9,[0004:01]111,123456789123453,,,,0102,11,90,0,3,38922,14V1,25.11.09-10:16:20,25.11.09-10:16:27,[0000:01]9,[0006:01]111,123456789123451,,,,0102,7,1f,0,,3663,10Table 11.2 Call Log Entries (continued)Column Description
FEATURE PACKAGESCHAPTER 11224iGATE 15.0. Revised: 2009.Example: The following example shows the pabx.cfg configuration file changed according to the formula:Differentiating Between SIM CardsThe CDR can contain the IMSI (International Mobile Subscriber Identity), which identifies each SIM card used:Example:The following example shows the pabx.cfg configuration file changed according to the formula:Example:Activating Peer Data for VoIP CallsTo generate a VoIP-call CDR entry that includes IP addresses for the remote device’s signaling and voice data, audiocodec and frame size, the entry VoipIpLogging=Yes must be included in the VoIP profile. If the entry alsocontains the mobile controller’s IMSI, it will appear before the IP addresses....Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0001]Subscriber01=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0002]Subscriber02=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0003]Subscriber03=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0004]Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0005]Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0006]Subscriber06=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0007]Subscriber07=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0008]Subscriber08=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0009]Subscriber09=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0010]Subscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0011]Subscriber11=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0012]Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0013]Subscriber13=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0014]Subscriber14=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0015]Subscriber15=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0016]...V1,25.11.09-10:35:16,25.11.09-10:35:26,[0000:01]9,[0004:01]111,123456789123451,,,,0102,10,1f,0,3,38922,14...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber01=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber02=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber03=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber04=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber06=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber07=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber08=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber09=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber11=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber12=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber13=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXTSubscriber14=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXT...If you remove the keyword IMSI from the pabx.cfg, you must restart the system.ii
FEATURE PACKAGESCHAPTER 11225iGATE 15.0. Revised: 2009.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 andframe size. CDRs for Callback and Two-Stage CallsIn the case of CDR entries for DLA/Callback calls, the beginning and ending times for the first call leg is alwaysused as the call time. The call time in seconds appears first for the first leg, followed by a slash and the connectiontime for the second leg.Example:Specific Cause ValuesThe iGATE will generate cause values that represent an event, such as exceeding a defined limit:11.4.2.2 MISSED CALLS LISTAll incoming calls that are not connected can be recorded in a list to facilitate return calls. Recording is activatedusing the failedlog=<name> entry in the pabx.cfg. Specify a file name, e.g. failedlog=failed.log. Once this settingis made, recording begins at once.[Voip:DF]VoipDirection=IOVoipPeerAddress=192.168.0.2VoipIpMask=0xffffffffVoipCompression=g729 t38VoipMaxChan=30VoipSilenceSuppression=Yes VoipSignalling=0VoipTxM=4VoipIPLogging=YesV1,24.11.09-16:52:20,24.11.09-16:52:22,[0008:01]401419,[0006:01]IN777,123456789123451,172.20.25.103:172.20.25.103,G711a,20,0101,2,10,0,,34193,11V1,24.11.09-17:15:29,24.11.09-17:15:57,[0002:01]CB,[0008:01]DLA,,172.20.25.103:172.20.25.103,G711a,20,0102,28/3,90,0,,,0a One of the following limits has been reached: Unit limit defined in the port’s subscriber lineUnit limit per SIM assignment via vGATE 0b Maximum call duration assigned via vGATE has been reached0c Maximum call duration based on mapping entry settings has been reached0d Maximum number of minutes per SIM assignment via vGATE has been reached10, 1f Normal call termination (disconnected by calling party)To avoid sending these values as the reason for call teardown, translate the cause values to standard values Chapter 8.12 >ii
FEATURE PACKAGESCHAPTER 11226iGATE 15.0. Revised: 2009.Each line represents an unaccepted incoming call with the following information separated by commas:Sample Failed LogThe example below shows a sample failed log file:The reason the connection could not be established is specified using DSS1 codes:91 – (user busy)ff – call not answered (disconnected by calling party)Table 11.3 Failed Log Entries Column Description0Version1Start time (format DD.MM.YY-hh.mm.ss)2Source. The following format applies: [node number:automatically set internal channel number]3Destination. The following format applies: [node number:automatically set internal chan-nel number]4IMSI5IP logging signaling: RTP6Audio codec used7Frame size8Service indicator (cf. Chapter 11.4.2 on page 221 >)9Cause values10 Call duration (if the call does not result in an Alerting, the entry will be -1)11 Number of call attempts12 Cell ID13 RSSIV1,24.11.09-16:13:08,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,9V1,24.11.09-16:33:34,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,12V1,24.11.09-16:35:19,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:35:59,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:37:29,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:39:17,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,ff,7,1,34193,11
FEATURE PACKAGESCHAPTER 11227iGATE 15.0. Revised: 2009.When callback with DTMF is configured and no connection is established to the B subscriber, an entry recordingthe A subscriber’s 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 andthe second one is the RTP address.The IMSI is written behind the IP addresses if the keyword IMSI is defined in thepabx.cfg:Example:In the case of missed-call entries for DLA/Callback calls, dur is the connection time for the first leg.Example:11.4.2.3 SENDING CDRS VIA E-MAILWith 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 inChapter 5.2.2 >. The sender is given as cdr and the system’s 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> @<domain>.A space must appear between cdr.log and @<account>; @<domain> is optional. You can also send CDR entriesvia e-mail to an e-mail recipient. Enter an @ sign to send each CDR entry as e-mail: Log=/data/cdr.log @<e-mail account>@<domain>If you enter a ! the entire cdr.log will be sent as an e-mail attachment:Log=/data/cdr.log !<e-mail account>@<domain>V1,24.11.09-16:39:17,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,ff,7,1,34193,11V1,24.11.09-16:52:20,24.11.09-16:52:22,[0008:01]401419,[0006:01]IN777,262032441017556,172.20.25.103:172.20.25.103,G711a,20,0101,2,10,0,,34193,11V1,25.11.09-14:11:10,[0002:01]CB,DLA,,,,,0102,11,14,1,,
FEATURE PACKAGESCHAPTER 11228iGATE 15.0. Revised: 2009.11.5 SMS GATEWAYThe SMS Gateway allows you to use your iGATE to send and receive SMS. The following functions are possible withthis feature package:Sending SMS via e-mailReceiving SMS to e-mail, SMS or to a fileSending and receiving USSD text messagesSetting up connections using e-mailSending automatic SMS for unconnected calls11.5.1 SENDING SMS VIA E-MAIL This function makes it possible to send SMS via a iGATE with an ordinary e-mail client. SMS messages are recordedin the CDR log with the service indicator 0500. The destination address with the keyword SMS, the call number,the @ sign and the IP address or the IP name of the iGATE must be entered.In the following example, an SMS is sent to the mobile number 015553456789, whereby sms-mail.server.de mustcorrespond with the IP address 172.172.172.172:Example: SMS015553456789@172.172.172.172 orSMS015553456789@sms-mail.server.deThe SMS text must be entered in the text box. The subject box is not used. If the e-mail program supports sendingthe same e-mail to more than one address, the SMS messages are sent in intervals of one second. The iGATE’salgorithms evenly distribute the SMS messages to the available mobile modules.If the iGATE rejects the SMS, an e-mail alerting an aborted SMS will be transmitted to the sender and the attemptwill be entered in the corresponding log file (failedlog=). If transmission is successful, a positive response will besent when the SMS is accepted by the SMS service center. sent will then appear in the subject dialog. A correspond-ing CDR will be entered with a destination address beginning with SMS.A request to set up a connection with the service ’telephony’ and the element ’user-to-user’ enables the SMS textto be sent to the iGATE. All iGATEs are supported that allow for SMS messages to be sent by the process describedabove. According to the restrictions of the ISDN signaling protocol, text length is limited to approximately 110-120characters. Longer texts will be cut off accordingly.The following entry must appear in the route.cfg configuration file for SMS transmission to be possible: Ma-pAllSMS=<port number>.Bear in mind that the parameters for connection to the SMTP server must be config-ured in the pabx.cfg’s [Mail] section (cf. 5.2.2 on page 77 >).To use this function, you must first set the parameter <smsc> in the pabx.cfg (cf. Table 5.15 on page 68 >).iiii
FEATURE PACKAGESCHAPTER 11229iGATE 15.0. Revised: 2009.Sent SMS will also be recorded if the call log is active on the system. The formats are describe inChapter 11.4.2.1 > and Chapter 11.4.2.2 >.Example 1 In the following example, SMS-transmission to the number 01721111111 from the e-mail ac-count j.smith was successful: Example 2 In the following example, SMS-transmission to the number 01721111111 from the e-mail ac-count j.smith was unsuccessful. the output -1 as cause value means that no routing entry wasconfigured: 11.5.2 RECEIVING SMS MESSAGES This function makes it possible to receive SMS messages via a mobile gateway with an ordinary e-mail client, toforward them to another mobile telephone, or to save them to a file. 11.5.2.1 SMS TO E-MAILThe destination number in the iGATE system must correspond with an e-mail account. The e-mail recipient’s namecontains the keyword ’sms’ and the destination number. The subject box contains the SIM card’s IMSI and the call-er’s number.Example:From: sms262124915553230618@gsm.teles.deSubject: SMS 262123203500514 4915553230618A mapping entry must indicate an e-mail account with a prefixed @. The following syntax is used:Restrict<port>=@<addressee> 05As an alternative, the @ sign can be substituted with a colon (:) in the recipient’s address. If only a destinationaccount is given, the configured domain name is used.11.5.2.2 SMS TO SMSThis configuration makes it possible to forward SMS messages via a mobile gateway to another mobile telephone.Restrict<port>=@-><port><mobile number> 0512.07.06-09:59:10,12.07.06-09:59:11,SMS01721111111,j.smith,0500,1,06,012.07.06-09:04:11,SMS01721111111,j.smith,0500,00,-1,0Bear in mind that you must set the service type in all identical restrict entries.Example: In the following example, all incoming voice calls are routed to the opera-tor incoming SMS messages are forwarded to the email account sysadmin:Restrict26202=100 01Restrict26202=@sysadmin 05ii
FEATURE PACKAGESCHAPTER 11230iGATE 15.0. Revised: 2009.Example:11.5.2.3 SMS TO FILEUsing this configuration, you can save SMS messages via a mobile gateway to a file.Make the following entry in the pabx.cfg:MsgLog=/data/msg.logThe following entry in the Route.cfg is also required:Restrict<port>=@FILE 0511.5.3 INCOMING USSD (UNSTRUCTURED SUPPLEMENTARY SERVICES DATA)Incoming USSD can either be saved to a file, sent as an SMS to an e-mail address or to a telephone that supportsthis service.Make the following entry in the pabx.cfg:MsgLog=/data/msg.logThe following entry in the Route.cfg is also required:Restrict<port>=@FILE 0611.5.4 SENDING MESSAGES VIA E-MAILThis function makes it possible to send text messages via the ISDN signaling channel gateway. The destination ad-dress with the keyword MSG, the @ sign and the IP address or the IP name of the iGATE system with mobile gatewaymust be entered.In the following example, a message is sent to the call number 0123456789, whereby msg-mail.server.de mustcorrespond with the IP address 172.172.172.172:Example: MSG0123456789@172.172.172.172 orMSG0123456789@msg-mail.server.deThe message must be entered in the text box. The subject box is not used. If the e-mail program used supportssending the same e-mail to more than one address, the messages are sent in intervals of one second. The iGATEsystem’s algorithms evenly distribute the messages to the available ISDN ports.If the recipient rejects the call, an e-mail alerting an aborted message will be transmitted to the sender and theattempt will be entered in the corresponding log file (failedlog=). If transmission is successful, a corresponding CDRwill be entered with a destination address beginning with MSG.Restrict20=@->200155512345678 05Restrict20=@FILE 06
FEATURE PACKAGESCHAPTER 11231iGATE 15.0. Revised: 2009.A request to set up a connection with the service ’telephony’ and the element ’user-to-user’ enables the messageto be sent to the recipient. All terminal devices and PBXes are supported that allow for messages to be sent by theprocess described above. According to the restrictions of the ISDN signaling protocol, text length is limited to ap-proximately 110-120 characters. Longer texts will be cut off accordingly.11.5.5 SETTING UP CONNECTIONS VIA E-MAILThis function sets up a connection between subscriber A and subscriber B via e-mail. Subscriber A is identified byan e-mail address and is dialed first. Subscriber B is called when the connection to subscriber A has been set up. A connection can be set up via e-mail with the keyword ’CALL,’ the destination number, the @ sign, and the IPaddress or the iGATE system’s IP name.The following example shows a connection with the destination number 0123456789, whereby msg-mail.serv-er.de must correspond with the IP address 172.172.172.172.Example: CALL0123456789@172.172.172.172 orCALL0123456789@msg-mail.server.deAny text contained in the text box will be sent to subscriber A as user-to-user information. The subject box is notused.Subscriber A is identified by an e-mail address and must be activated in the iGATE system. The subscriber’s namemust appear before the @ sign. This name must be assigned a corresponding MapOut command.Example: Subscriber’s e-mail address is meier@server.de. Subscriber’s extension is 555. Configure Ma-pAll@555=meier.In addition to CTI capability, this function allows for callback via e-mail.11.5.6 DISPLAYING INCOMING CALLSWith this function, you can use e-mail to signal incoming calls. Two signaling types are possible:Display all incoming calls that receive a busy or ringing signal. Enter the keyword CTI[001.000.000.000]in the VoIP controller’s Subscriber line of the iGATE system’s pabx.cfg configuration file.Display all unsuccessful incoming calls (callback list) that receive a busy signal or remain unanswered.Enter the keyword CTI[002.000.000.000] in the VoIP controller’s subscriber line of the iGATE system’spabx.cfg configuration file.The destination is the address of the called subscriber configured in a corresponding map entry. A callback can beinitiated when the recipient responds to the e-mail.The following entry must appear in the route.cfg:MapAllMSG=<port>ii
FEATURE PACKAGESCHAPTER 11232iGATE 15.0. Revised: 2009.11.5.7 SENDING AUTOMATIC SMS FOR UNCONNECTED CALLSWhen the iGATE is implemented in a corporate network and connected to a PBX or between a PBX and the outsideline, the following configuration entry in the pabx.cfg activates a feature, whereby the system automaticallysends an SMS message to dialed mobile numbers that are unreachable or not answering. A configurable text containing the callers OAD is sent in the SMS message, so that the mobile user knows whocalled him through the iGATE’s interface and can return the call. The parameter SMSInfo activates this feature. The text can be configured on an individual basis, and the caller’snumber is automatically generated when you enter %s. You must enter the text that is to be sent in quotationmarks: SMSInfo="<text>%s<text>"Example: In the following example, SMS messages for mobile users are generated only when calls cannotbe connected. The network prefix is 0155 and the LAIN is 26212. The company’s mobile prefixis 57777. No other mobile targets for mobile carriers with the LAIN 26212 and 26213 receive SMS, sincethe parameter VOICE has been defined in the mapping entry:pabx.cfg:route.cfg:11.6 PORTED NUMBER SCREENINGPorted Number LCR Extension is a function that enables you to map defined destination call numbers to other des-tination numbers or networks (number portability). This function is used to allow telecommunications subscribersto change carriers without having to change their telephone numbers.Number portability is used in the fixed network, as well as in the mobile network. Usually the numbers are mappedin their respective networks. Implementation of this information and the corresponding routing processes result insignificant cost savings, as tariff differences between calls to ’normal’ and ported subscribers are eliminated. No SMS will be generated for unconnected calls if the service code VOICE or DATA appears in the mapping entry.The SMS center number must be defined (cf. Table 5.15 on page 68 >), and the rout-ing entry for sending SMS must be configured.At least two SIM cards must be activated in the iGATE for this feature to work.SMSInfo="You got a call from %s . Please call back."MapAllSMS=26212MapAll015557777=|26212015557777<<17MapAll01555=|2621201555<<17 VOICEMapAll01556=|2621201556<<17 VOICEMapAll01444=|2621301444<<17 VOICEMapAll01445=|2621301445<<17 VOICEii
FEATURE PACKAGESCHAPTER 11233iGATE 15.0. Revised: 2009.The database of ported numbers runs on the iMNP, which provides the data online for the entire network. You canalso choose an external provieder.The iGATE automatically routes calls through specific ports, so that all calls through the same carrier (includingported numbers) are routed through the port containing that carrier’s SIM card.11.6.1 SYSTEM REQUIREMENTSPorted number screening requires the following:An active license package for number portability.A iMNP server or another appropriate server11.6.2 ROUTING AND CONFIGURATIONTo connect to the number portability database, you must set the entries described in Chapter 5.2.3 >.An appropriate routing entry in the route.cfg file is required to activate Ported Number LCR Extension. This includesactivation of digit collection and the following mapping configuration:...DTMFWaitDial=<sec>MapAll<num>=|$ph<<<count>MapAllph=|D@<num><<01The routing entries for the iMNP results contain the keyword QN, followed by the query result, an equal sign andthe controller:MapAllQN<query>=<controller>...Example: The following example uses digit collection (11 digits plus $ph). Every incoming call with a lead-ing digit of 0 results in an iMNP query. The SIM-card LAINs are used instead of controller num-bers. All numbers that come back from the iMNP with the LAIN for Carrier_1 (26211) are thenrouted through Carrier_1’s SIM card with CLIR. The same applies for Carrier_2 (26212),Carrier_3 (26213) and Carrier_4 (26214). Numbers that the iMNP sends back as non-existing(00000) are rejected. Numbers that may exist but are not found in the database (99999) are rout-ed as they come in (normal). If the iMNP does not respond within two seconds (D@0), the call
FEATURE PACKAGESCHAPTER 11234iGATE 15.0. Revised: 2009.is routed as it comes in, whether it is ported or not: DTMFWaitDial=5MapAll0=|$ph<<14MapAllph=|D@0<<01MapAllQN26211=#26211MapAllQN26212=#26212MapAllQN26213=#26213MapAllQN26214=#26214MapAllQN00000=&81MapAllQN99999=$normalMapAllD@0=$normal1; not in Database ;Carrier_1MapAllnormal0151=#262110151MapAllnormal0160=#262110160MapAllnormal0170=#262110170MapAllnormal0171=#262110171MapAllnormal0175=#262110175;Carrier_2MapAllnormal0152=#262120152MapAllnormal0162=#262120162MapAllnormal0172=#262120172MapAllnormal0173=#262120173MapAllnormal0174=#262120174;Carrier_3MapAllnormal0155=#262130155MapAllnormal0163=#262130163MapAllnormal0177=#262130177MapAllnormal0178=#262130178;Carrier_4MapAllnormal0159=#262140159MapAllnormal0176=#262140176MapAllnormal0179=#262140179
OPTIONAL FUNCTION MODULESCHAPTER 12235iGATE 15.0. Revised: 2009.12 OPTIONAL FUNCTION MODULESThe following modules are included:GUISNMP agentDNS forwarderipupdate - DynDNS clientSince these features are only required in individual cases, they are not part of the default software packet. Theycan be installed as stand-alone modules for the desired function. The description of the functionality of individualmodules appears in their respective chapters.12.1 OVERVIEWThe modules can be downloaded using FTP. The access data for each module is as follows:GUIftp://195.4.12.80user: httpdpassword: httpdDNS Forwarderftp://195.4.12.80user: dnsmasqpassword: dnsmasqsnmp agentftp://195.4.12.80user: snmppassword: snmpipupdateftp://195.4.12.80user: ipupdatepassword: ipupdateInstall the respective software package on the iGATE using GATE Manager. For a description of how to update thesoftware, please refer to Chapter 10.3 >. Make sure the module’s file ending is correct before installation. Thenumber in the file ending shows the starting order of the modules. Do NOT change this number if it is 0! All othermodules can simply be numbered in ascending order. For instance, the ending for the optional function module will be tz2 or higher:tz2tz3Following completion of transmission, you must adjust the module’s configuration and restart the iGATE. Once youhave restarted the system, you can use the required features.
OPTIONAL FUNCTION MODULESCHAPTER 12236iGATE 15.0. Revised: 2009.12.2 GRAPHICAL USER INTERFACEThe GUI is a user-friendly tool that can be used by carriers, administrators and individual users to configure theiGATE. For a detailed description of the GUI, please see Chapter 4.12.2 >12.3 SNMP AGENTThis 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 errorrecovery messages are sent via SNMP trap. Traps are generated for all line or mobile ports. The running number in the trap corresponds with the port. Themodule 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:If more than one pppoe<x> profile is configured, the number will also increase.Bear in mind that the keyword ALARM must be entered in the appropriate PRI, BRI or mobile port’s Subscriber linein the pabx.cfg. The MIBs (Management Information Bases) are included on the product CD in the folder MIB. Themodule name snmpd.tz0 must have the ending tz0!The following settings are possible in the section [snmpd]: Table 12.1 Traps for IP Interfaces Trap Number Interface0Ethernet 11Ethernet 22 Loopback3 xppp= (if used)4 pppoe= (if used)Table 12.2 Settings in the Section [snmpd]Parameter DefinitionPort=<port> Defines the target port for the trap server (default 161).TrapServer=<ip addr> Enter the SNMP trap server’s IP address. Example for listing more than one: TrapServer=192.168.0.10 192.168.0.12Community=<password> Enter a password for a community (group). The default password is public.
OPTIONAL FUNCTION MODULESCHAPTER 12237iGATE 15.0. Revised: 2009.12.4 DNS FORWARDERWith this module, the system can function as a DNS server for the clients in the local network. The system in thelocal network sent the DNS query to the iGATE, which forwards the queries to a known DNS server address if novalid entry for the query is known. The advantage is that the clients always enter the iGATE’s address as DNS server address, so that no public DNSserver address is required. The iGATE functions in this scenario as a router. Of course, the DNS server’s address can also be transmitted to the clients using the integrated DHCP server. If theiGATE 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 pa-rameter NameServer. The DNS server’s address that is negotiated through this connection will be used.12.5 IPUPDATE - DYNDNS CLIENTThis function allows you to assign a defined hostname to an IP address that changes dynamically. That means thatyou can always reach a device or service through the public IP network, even if, for example, it is a common DSLconnection with dynamic IP address allocation. Several providers support this service.
OPTIONAL FUNCTION MODULESCHAPTER 12238iGATE 15.0. Revised: 2009.Make the following entries in the system’s ip.cfg, in the [DynDNS] section: 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 iGATE works as DSL router and the dynami-cally allocated IP address of the PPPoE interface is used:Table 12.3 pabx.cfg: DynDNS DynDNS Parametersservice=<type>Specifies which provider is used. The following providers are supported:dhsdyndnsdyndns-staticdynsezipeasydnseasydns-partnergnudipheipv6tbhnpgpowodstzozoneedithttp://www.dhs.orghttp://www.dyndns.orghttp://www.dyns.cxhttp://www.ez-ip.nethttp:/www.easydns.comhttp://www.gnudip.cheapnet.nethttp://www.hn.orghttp:www.justlinux.comhttp://ods.orghttp://www.tzo.comhttp://zoneedit.comuser=<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.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.
OPTIONAL FUNCTION MODULESCHAPTER 12239iGATE 15.0. Revised: 2009.Included in the possible uses for this feature is remote access to the iGATE when the IP connection does not havea fixed IP address. In this case, you can access the system, for example with the GATE Manager, if the host nameis used in the Remote Number dialog. Example entry in the Remote Number dialog: IP:host.domain.de[DynDNS]service=dyndnsuser=user:pwdhost=host.domain.deinterface=pppoe0max-interval=2073600
TELES AG InformationstechnologienErnst-Reuter-Platz 810587 Berlin, GermanyPhone: +49 30 399 28-00Fax: +49 30 399 28-01E-mail: sales@teles.comhttp://www.teles.com/

Navigation menu