TELES iGATE v4 9

TELES.
iGATE Systems Manual

Version 4.8
Berlin
TELES AG provides this document as is, with no representations or warranties, either explicit or implied, including but not limited to the implied warranties of merchantability, title, or fitness for a particular purpose.
TELES AG reserves the right to make changes in product software, hardware, or documentation at any time, with no obligation to inform any persons or entities of such changes. Every effort has been made to ensure that the information in this manual is accurate. However, TELES AG assumes no responsibility for any losses, whether electronic, financial or other, that might accrue from inadvertent inaccuracies that the software or documentation might contain.
The hardware and software described in this publication is protected by international copyright law. Use is intended solely for the legitimate owner. Unauthorized distribution or use may result in civil and criminal penalties and will be prosecuted.
Copyright 2004 TELES AG Berlin. All rights reserved. TELES, IntraSTAR, Intra*, iSWITCH and iGATE are registered trademarks of TELES AG. All other trademarks used are the property of their respective owners.
Contents
Contents
1 Safety and Security Precautions .................................................... 1
1.1 Safety Measures ............................................................................................... 1 1.2 Tips for EMC Protection .................................................................................. 1 1.3 System Security ............................................................................................... 1 1.4 Servicing the System ....................................................................................... 2 1.4.1 Replacing Components............................................................................... 2 1.4.2 Protecting the Operating System ................................................................ 3 1.5 CDR Files .......................................................................................................... 3 1.6 Network Security .............................................................................................. 4
TELES.iGATE GSM ....................................................................... 6
2.1 Overview ........................................................................................................... 6 2.2 Features ............................................................................................................ 7 2.3 How TELES.iGATE Works ............................................................................... 7 2.4 Supported Implementation Scenarios ............................................................ 8 2.5 Installation ...................................................................................................... 11 2.5.1 Checklist.................................................................................................... 11 2.5.2 TELES.iGATE Hardware Installation ........................................................ 12 2.5.2.1 ISDN Wiring ........................................................................................ 16 2.5.3 Basic Configuration of the TELES.iGATE ................................................. 17 2.5.3.1 PRI Configuration Changes ................................................................ 17 2.5.3.2 BRI Configuration Changes ................................................................ 18 2.5.3.3 Configuration of the GSM Interface .................................................... 18 2.5.3.4 Configuration of the IP Interface ......................................................... 18 2.5.3.5 Configuration of the VoIP Interface..................................................... 19 2.5.3.6 Remote Access................................................................................... 20 2.5.3.7 Initial Routing Entries .......................................................................... 21 2.6 Configuration of the TELES.iLCR 4 GSM Board ......................................... 22 2.6.1 Configuration in the startpbx.bat file .................................................. 22 2.6.2 Configuration in the pabx.cfg File .......................................................... 25 2.6.3 Customized Configuration for TELES.iGATEs.......................................... 31 2.6.3.1 Module Distribution of Various Mobile Networks ................................ 31 2.6.3.2 Network-Specific GSM Routing .......................................................... 34 2.6.3.3 Generating and Retrieving CDRs ....................................................... 36 2.6.3.4 ASR Calculation and Resetting Statistic Values ................................. 37 2.6.3.5 Calling Line Identification Restriction (CLIR) ...................................... 39 2.6.3.6 Incoming Voice Calls from GSM ......................................................... 39
2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004
Page i
Contents 2.6.3.7 Setting Time Quotas by Blocking Ports...............................................41 2.6.3.8 Defining Time Limits for Calls..............................................................44 2.6.3.9 Switching SIMs after Each Call ...........................................................44 2.6.3.10 Time-Controlled Configuration ..........................................................45 2.6.3.11 Checking Ports/GSM Channels.........................................................46 2.6.3.12 Blocking Ports ...................................................................................47 2.6.3.13 Deactivating Class 2 Re-Routing ......................................................48 2.6.3.14 Recharging Pre-Paid SIMs................................................................48 2.7 GSM Port Status ..............................................................................................49 2.8 The SIM-Card Carrier Module ........................................................................50 2.9 TELES.iLCR 4 GSM Board SIM-Card LEDs ..................................................52 2.10 Connection to a TELES.vGATE ...................................................................54
3 Global System Features ................................................................55

3.1 Signaling and Routing Features ....................................................................55 3.1.1 Rejecting Data Calls and Specified Speed Dialing .................................... 55 3.1.2 Routing CLIP and CLIR Calls .................................................................... 55 3.1.3 Routing Calls without CLIR........................................................................ 56 3.1.4 Setting National/International in the Destination Number with DSS1 ........ 56 3.1.5 Setting a Default OAD ............................................................................... 56 3.1.6 Routing Profiles ......................................................................................... 56 3.1.6.1 Limiting Number of B Channels...........................................................57 3.1.7 Conversion of Call Numbers...................................................................... 57 3.1.8 Digit Collection (Enblock/Overlap Receiving) ............................................ 58 3.1.9 Changing Cause Values............................................................................ 58 3.2 Functions with the TELES.iLCR IP Board ....................................................59 3.2.1 ftp to the Host via the TELES.iLCR IP Board.......................................... 59 3.2.2 Connection to an SMTP Server ................................................................. 61 3.2.3 Sending SMS via E-mail ............................................................................ 62 3.2.4 Receiving SMS Messages......................................................................... 63 3.2.4.1 SMS to E-Mail .....................................................................................63 3.2.4.2 SMS to SMS........................................................................................64 3.2.4.3 SMS to File..........................................................................................64 3.2.5 Incoming USSD (Unstructured Supplementary Services Data) ................ 64 3.2.6 Sending Messages via E-mail ................................................................... 64 3.2.7 Setting Up Connections via E-mail ............................................................ 65 3.2.8 Displaying Incoming Calls ......................................................................... 66 3.2.9 Generating Online CDRs........................................................................... 67 3.2.9.1 Sending CDRs via TCP/IP ..................................................................67 3.2.9.2 Sending CDRs via E-Mail....................................................................68 3.2.10 Alarm Notification .................................................................................... 68 3.2.10.1 SNMP Support ..................................................................................68 3.2.10.2 Sending Alarm Messages via E-mail or SMS....................................69 3.2.11 Automatic Call Generation....................................................................... 70 3.2.12 Setting the Systems Clock with SNTP .................................................... 73
Page ii
Contents 3.2.13 DTMF Tone Detection and Call Setup .................................................... 74 3.2.14 Callback via HTML .................................................................................. 76 3.3 Number Portability and Black and White Lists ............................................ 78 3.3.1 Activation License ..................................................................................... 78 3.3.2 Number Portability..................................................................................... 80 3.3.2.1 System Requirements......................................................................... 80 3.3.2.2 Database............................................................................................. 80 3.3.2.3 Routing and Configuration .................................................................. 81 3.3.3 Black and White Lists................................................................................ 83 3.4 SS7-Specific Settings .................................................................................... 85 3.4.1 Activation License for the SS7 Protocol .................................................... 87
Page iii
Contents
Page iv
Safety and Security Precautions
Safety Measures
Please be sure and take time to read this section to ensure your personal safety and proper operation of your TELES Infrastructure System. To avoid personal injury or damage to the system, please follow all safety instructions before you begin working on your TELES Infrastructure System. TELES Infrastructure Systems are CE certified and fulfill all relevant security requirements. The manufacturer assumes no liability for consequential damages or for damages resulting from unauthorized changes.
1.1
Safety Measures
Danger of electric shock - the power supplies run on 230 V. Unplug the TELES Infrastructure System from its power source before working on the power supply or extension socket. Make sure to install the system near the power source and that the power source is easily accessible. Bear in mind that telephone and WAN lines are also energized and can cause electric shocks. Wire your system using only the cables included in the package contents. Use only proper E1 and Ethernet cables. 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. Changes in the device are not permitted. Be sure to respect country-specific regulations, standards or guidelines for accident prevention.
1.2
Tips for EMC Protection
Use shielded cables. Do not remove any housing components. They provide EMC protection.
1.3
System Security
This section describes all points crucial to the TELES Infrastructure Systems system security.
Page 1
Servicing the System
The systems 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: Location: Make sure you install the system in a clean, dry, dust-free location. If possible, the site should be air-conditioned. The site must be free of strong electrical or magnetic fields, which cause disrupted signals and, in extreme cases, system failure. Temperature: The site must maintain a temperature between 0 and 45C. Be sure to guard against temperature fluctuations. Resulting condensation can result in short circuit. The humidity level may not exceed 80%. To avoid overheating the system, make sure the site provides adequate ventilation. Power: The site must contain a central emergency switch for the entire power source. The sites fuses must be calculated to provide adequate system security. The electrical facilities must comply with applicable regulations. The operating voltage and frequency may not exceed or fall below what is stated on the label. Antenna: TELES.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.
1.4
Servicing the System
Regular servicing ensures that your TELES.System runs trouble-free. Servicing also includes looking after the room in which the system is set up. Ensure that the air-conditioning and its filter system are regularly checked and that the premises are cleaned on a regular basis.
1.4.1
Table 1-1
Replacing Components
Component Life Span Component Filter pads CPU fan Power adapter incl. 3.3 V Adapter 6 months 5 years 5 years Life span
Replace components according to the following table:
Page 2
Safety and Security Precautions Table 1-1 Component Life Span Component Fan Hard disk (SCSI) Hard disk (IDE) 5 years 5 years 3 years Life span
CDR Files
1.4.2
Protecting the Operating System
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 resulting from or in relation to such changes. Please thoroughly check any changes you or a third party have made to your configuration! Make sure your hard disk contains enough storage space. Downloading the log files and deleting them from the system on a regular basis will ensure your systems reliability. Be careful when deleting files that you do not delete any files necessary for system operation.
1.5
CDR Files
Call Detail Records are intended for analysis of the systems activity only. They are not designed to be used for billing purposes, as it may occur that the times they record are not exact.
Page 3
Network Security
1.6
Network Security
Every day hackers develop new ways to break into systems through the Internet. While TELES takes great care to ensure the security of its systems, any system with access through the Internet is only as secure as its user makes it. Therefore, to avoid unwanted security breaches and resulting system malfunctions, you must take the following steps to secure your 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 secure network segments. Access to the system via Telnet, FTP, HTTP, TELES.WinRemotePro or remote vGateDesktop must be password protected. 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. Protection against IP spoofing Automatic recognition of security breaches Logging of all attempts to access the system
The firewall must support the following features:
The firewall must be able to check the following information and only allow trusted users to access the TELES.System: IP source address IP destination address Protocol (whether the packet is TCP, UDP, or ICMP) TCP or UDP source port TCP or UDP destination port ICMP message type
For operation and remote administration of your TELES.System, open only the following ports only when the indicated services are used:
Service Protocol Port
For TELES.iGATE, TELES.VoIPGATE and TELES.iLCR FTP Telnet SMTP DNS Forward HTTP SNTP TCP TCP TCP UDP TCP UDP 21 (default, can be set) 23 25 53 80 (default, can be set) 123
Page 4
Network Security
Service SNMP H.225 Registration, Admission, Status H.225 Signaling Radius Radius Accounting TELES.WinRemotePro SIP Signaling RTP TELES.iGATE to TELES.iGATE Communication TELES.vGATE Control Unit UDP UDP TCP UDP UDP TCP UDP UDP UDP
Protocol 161
Port
1719 (default, can be set) 1720 (default, can be set) 1812 1813 4445 (default, can be set) 5060 (default, can be set) 29000-29120 (default, can be set) 29417
TCP
57343
For TELES.vGATE Control Unit FTP Telnet MySQL database TELES.iGATE signaling Remote vGateDesktop Remote vGateDesktop (read only) TCP TCP TCP TCP TCP TCP 21 23 3306 57342, 57343 57344 57345
For TELES.vGATE Sim Unit TELES.vGATE Control Unit plus TELES.iGATE TCP 51500
Note:
Connection from a TELES.vGATE Control Unit to a TELES.iGATE requires ICMP access. The TCP filters listed above are activated in the TELES.vGATE Control Units default configuration.
Page 5
Overview
TELES.iGATE GSM
2
2.1
TELES.iGATE GSM
Overview
Mobile phone charges have become an important cost factor for many carriers and companies. Connections from the fixed network to mobile networks share a considerable amount of these costs. The TELES.iGATE can help reduce these costs up to 70%, because calls from mobile network to mobile network cost significantly less than calls from the fixed network to mobile networks. Fixed-to-mobile calls that travel through the TELES.iGATE are routed and billed as if they occurred within the same mobile network. The TELES.iGATE provides direct access to the GSM network with up to 60 channels 4 GSM channels per TELES.iLCR 4 GSM Board, 15 TELES.iLCR 4 GSM Boards per TELES.iGATE or x TELES.iLCR 4 GSM Boards as extension boards for the TELES.iLCR. The TELES.iLCR Antenna Splitter Board combines the antennas so that only one or two antennas leave the system. The TELES.iGATE VoIP comes with a TELES.iLCR VoIP Board, so connection of the mobile gateway occurs by VoIP. The TELES.iGATE VoIP combines the cost savings resulting from implementation of the TELES.iGATE with those of Voice over IP transmission. TELES.iGATEs and TELES.iGATE VoIPs can be set up in various national or international locations. Note: This manual applies only for second generation TELES.iGATEs. First generation TELES.iGATEs are described in the TELES Infrastructure Systems Manual 4.5.
Page 6
TELES.iGATE GSM
Features
2.2

Features
Conversion of 2 x E1 to up to 60 GSM channels and vice versa Can handle up to 24 SIM cards on 4 GSM channels (SIMs can be randomly distributed at will) Requires only two antennas for 60 GSM channels with TELES.iLCR Antenna Splitter Board Centralized SIM management with TELES.vGATE (optional) Call distribution/rerouting of temporarily unavailable GSM channels Automatic use (configurable) of the defined SIM cards per GSM 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 Generates CDRs Remote administration via ISDN Remote administration via Ethernet (optional) Time-controlled configuration Functions as an LCR Optional callback function supported Optional Direct Line Access function Optional SS7 Optional Number Portability
2.3
How TELES.iGATE Works
The TELES.iGATE is connected to the PSTN or an IP network and to the GSM network. During outgoing calls from the PSTN to GSM, dialed digits are compared with the routing table entries for various mobile networks. The calls are then routed through the corresponding SIMs in the TELES.iGATE and forwarded to the number dialed. Only the connection from the SIM in the TELES.iGATE to the mobile number in the same mobile network is charged.
Page 7
Supported Implementation Scenarios
TELES.iGATE GSM
2.4
In 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 are connected to the carrier network. The carrier network routes mobile connections to the individual mobile gateways, which then terminate the mobile calls. b) Integration in a carrier network by VoIP: One or more mobile gateways are connected to the carriers IP backbone or the public Internet by VoIP. The carrier network routes mobile connections to the individual mobile gateways, which then terminate the mobile calls accordingly. c) Connection to a carrier network for dial-up implementation: One or more mobile gateways are connected to the carrier network. The mobile gateway routes the mobile subscribers calls to the carrier network, which then terminates these mobile calls nationally or internationally. d) Last mile connection by GSM: The mobile gateways are set up at specific locations. The mobile gateway can multiplex the available mobile channels, as well as directly connect analog and/or ISDN subscribers (voice connections only).
Page 8
TELES.iGATE GSM
e) Least Cost Routing for termination of mobile calls: The mobile gateway with integrated LCR is set up between the existing PBX and the PSTN. The systems LCR recognizes calls to the mobile network and sends them through the mobile gateway to the mobile network. f) Mobile backup solutions: The mobile gateway is attached to an existing PBX. If, for example, a trunk or individual network components should fail, the connection will be set up using the mobile gateway. The mobile network can terminate national and international fixed network calls, as well as mobile calls. Incoming calls can be forwarded to the PBX through the call numbers of the mobile gateways SIM cards. g) Least Cost Router for international roaming: The mobile gateway is attached to an existing PBX. Individual extensions can be rerouted in the systems Least Cost Router. This new route can be set up with a transmitted SMS, which enables a subscriber in a corporate network to route his extension to a mobile device.The subscriber, who is abroad, can use a local SIM card and log onto the mobile gateway with a transmitted SMS. Calls to this subscriber are now routed by the mobile gateway through the available fixed network to a local mobile number. h) GSM connection for objects in motion: The mobile gateway is installed on a moving object (e.g. ship or transport truck). The mobile gateway contains several GSM SIM cards with access to various local mobile networks in the individual countries in which the object moves. GSM access is active
Page 9
TELES.iGATE GSM
only if the SIM cards have access to the corresponding mobile network. The mobile gateway routes all calls only to the corresponding active SIM cards. Calls are always routed through the least expensive mobile network t a national or international subscriber. i) SMS connection by e-mail: The mobile gateway is connected by Ethernet to the IT network. It implements an SMTP server (e-mail server). E-mail messages sent to this SMTP server are forwarded to the recipient as SMS messages through the mobile gateway. j) Connection to a centralized SIM server (TELES.vGATE): The mobile gateways are integrated in the TELES.vGATE through the IP network. All SIM cards in the TELES.vGATE network are installed in and maintained from a central server, so that it is no longer necessary to install SIM cards into each TELES.iGATE. The vGateDesktop makes it possible to assign SIMs virtually to random ports and various times without physically removing the SIMs from the TELES.vGATE Sim Unit.
Page 10
TELES.iGATE GSM
Installation
2.5
Installation
This section contains information on basic installation and configuration of your TELES.iGATE. Implementation of individual scenarios require adjustments to the appropriate interfaces. Tips for basic settings are described here. Links to relevant chapters are provided for more specific configuration changes.
2.5.1
1. 2. 3. 4. 5. 6. 7. 8.
Checklist
The following checklist provides step-by-step installation instructions. Check the package contents Install the device Connect antennas and insert SIM cards Connect the E1 trunks Check functionality (using the LEDs) Set the IP address Secure the LAN connection Secure connection with the configuration program Make sure the package contents are complete and undamaged before you begin installation of your TELES Infrastructure System. Immediately report any visible transport damages to customer service. If damages exist, do not attempt operation without customerservice approval.
Note:
Page 11
Installation
TELES.iGATE GSM
2.5.2
TELES.iGATE Hardware Installation
TELES.iGATE for 4-32 GSM Channels and TELES.iGATE 60 Figure 2-1 shows the rear view a TELES.iGATE for 4 to 32 GSM channels, which contains the following boards (from left to right). The TELES.iGATE 60 includes 7 additional TELES.iLCR 4 GSM Boards and an additional TELES.iLCR Antenna Splitter Board: CPU Board Additional BRI or PRI Board (optional) TELES.iLCR 3PRI Board TELES.iLCR 4 GSM Board 1 (for GSM channels 1-4) TELES.iLCR 4 GSM Board 2 (for GSM channels 5-8) TELES.iLCR 4 GSM Board 3 (for GSM channels 9-12) TELES.iLCR 4 GSM Board 4 (for GSM channels 13-16) TELES.iLCR Antenna Splitter Board (optional) TELES.iLCR 4 GSM Board 5 (for GSM channels 17-20) TELES.iLCR 4 GSM Board 6 (for GSM channels 21-24) TELES.iLCR 4 GSM Board 7 (for GSM channels 25-28) TELES.iLCR 4 GSM Board 8 (for GSM channels 29-32) TELES.iLCR IP Board (optional)
6
Figure 2-1
TELES.iGATE for 4-32 GSM Channels: Rear View
Page 12
TELES.iGATE GSM
Installation
Table 2-1 describes the numbered arrows shown in Figure 2-1.

Table 2-1 Number 1. 2. 3. TELES.iGATE for 4-32 GSM Channels: Assembly Description The correct port sequence from top to bottom (ports 1-4): TE, NT, NT, NT. The correct port sequence from top to bottom (ports 1-3): TE, NT, NT for the TELES.iGATE and TE, TE, NT for the TELES.iGATE 60. Each TELES.iLCR 4 GSM Board has a slot for a SIM-card carrier. Insert the SIMs in the SIM-card carrier and then insert the SIM-card carrier here (see Chapter 2.8 on page 50). NOTE: 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. If your TELES.iGATE has a TELES.iLCR Antenna Splitter Board, plug the antenna for TELES.iLCR 4 GSM Boards 1-4 in the upper SMA jack and the antenna for TELES.iLCR 4 GSM Boards 5-8 in the lower SMA jack. NOTE: Antennas connected to the TELES.iGATE must be installed by a qualified technician according to all necessary safety requirements and the antennas installation specifications. The antenna adaptor does not provide power surge protection. If you have a TELES.iLCR IP Board, connect the TELES.iGATE to the Ethernet here. Plug the power cord in here. Plug your keyboard into one of these two outlets. Plug your monitor in here. If you do not have a TELES.iLCR Antenna Splitter Board, plug an antenna cable into each of these SMA jacks. NOTE: Antennas connected to the TELES.iGATE must be installed by a qualified technician according to all necessary safety requirements and the antennas installation specifications. The antenna adaptor does not provide power surge protection.
4.
5. 6. 7. 8. 9.
Page 13
Installation
TELES.iGATE GSM
TELES.iGATE for 4-60 GSM Channels Connected to VoIP Network Figure 2-2 shows the rear view a TELES.iGATE for 4 to 60 GSM channels connected to the VoIP network, which contains the following boards (from left to right): CPU Board TELES.iLCR VoIP Board TELES.iLCR 3PRI Board TELES.iLCR 4 GSM Board 1 (for GSM channels 1-4) TELES.iLCR 4 GSM Board 2 (for GSM channels 5-8) TELES.iLCR 4 GSM Board 3 (for GSM channels 9-12) TELES.iLCR 4 GSM Board 4 (for GSM channels 13-16) TELES.iLCR Antenna Splitter Board (optional) TELES.iLCR 4 GSM Board 5 (for GSM channels 17-20) TELES.iLCR 4 GSM Board 6 (for GSM channels 21-24) TELES.iLCR 4 GSM Board 7 (for GSM channels 25-28) TELES.iLCR 4 GSM Board 8 (for GSM channels 29-32) TELES.iLCR 4 GSM Board 9 (optional, for GSM channels 33-36) TELES.iLCR 4 GSM Board 10 (optional, for GSM channels 37-40) TELES.iLCR 4 GSM Board 11 (optional, for GSM channels 41-44) TELES.iLCR 4 GSM Board 12 (optional, for GSM channels 45-48) TELES.iLCR Antenna Splitter Board (optional) TELES.iLCR 4 GSM Board 13 (optional, for GSM channels 49-52) TELES.iLCR 4 GSM Board 14 (optional, for GSM channels 53-56) TELES.iLCR 4 GSM Board 15 (optional, for GSM channels 57-60)
5
Figure 2-2
TELES.iGATE VoIP for 4-60 GSM Channels: Rear View
Page 14
TELES.iGATE GSM
Installation
Table 2-2 describes the numbered arrows shown in Figure 2-2.

Table 2-2 Number 1. 2. 3. TELES.iGATE VoIP for 4-60 GSM Channels: Assembly Description Connect the TELES.iGATE VoIP to the Ethernet here. The correct port sequence from top to bottom (ports): TE, TE, NT. Each TELES.iLCR 4 GSM Board has a slot for a SIM-card carrier. Insert the SIMs in the SIM-card carrier and then insert the SIM-card carrier here (see Chapter 2.8 on page 50). NOTE: 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. If your TELES.iGATE VoIP has a TELES.iLCR Antenna Splitter Board, plug the antenna for TELES.iLCR 4 GSM Boards 1-4 in the upper SMA jack of the first TELES.iLCR Antenna Splitter Board, the antenna for TELES.iLCR 4 GSM Boards 5-8 in the lower SMA jack of the same board and the antenna for TELES.iLCR 4 GSM Boards 9-12 in the top SMA jack of the second TELES.iLCR Antenna Splitter Board. Leave the bottom SMA jack of the second board empty. NOTE: Antennas connected to the TELES.iGATE must be installed by a qualified technician according to all necessary safety requirements and the antennas installation specifications. The antenna adaptor does not provide power surge protection. Plug the power cord in here. Plug your keyboard into one of these two outlets. Plug your monitor in here. If you do not have a TELES.iLCR Antenna Splitter Board, plug an antenna cable into each of these SMA jacks. NOTE: Antennas connected to the TELES.iGATE must be installed by a qualified technician according to all necessary safety requirements and the antennas installation specifications. The antenna adaptor does not provide power surge protection.
4.
5. 6. 7. 8.
Page 15
Installation
TELES.iGATE GSM
2.5.2.1
ISDN Wiring
If you are connecting a TELES.iGATE to E1 and need to change the assignment of an adapter from German TE to international NT or vice versa, assign the pins as follows. Cables included with the TELES.iGATE will be yellow for TELES TE, black for TELES NT, and green for TE and NT on the remote device:
Yellow Green
1 2 TX 3 RX 4 RX 5 TX 6 7 8 1 TX 2 TX 3 4 RX 5 RX 6 7 8
Terminal Interface
Network Interface
Green Black
1 2 TX 3 RX 4 RX 5 TX 6 7 8 1 RX 2 RX 3 4 TX 5 TX 6 7 8
Network Interface
Terminal Interface
TELES TE to TELES NT If you are connecting TELES TE to TELES NT, cables will be yellow and pin assignment will be as follows:
Yellow Yellow
1 2 TX 3 RX 4 RX 5 TX 6 7 8 1 2 3 TX 4 RX 5 RX 6 TX 7 8
Terminal Interface
Network Interface
Page 16
TELES.iGATE GSM
Installation
2.5.3
Basic Configuration of the TELES.iGATE
Following installation of the system and connection to E1 as described above, turn on the TELES.iGATE. After all drivers have loaded, the Status Program will appear. Enter Alt-F10 to call up port status. A MFE should appear in black for the appropriate ISDN controller (for a detailed description of Status Program commands and functions, see Chapter 6 of the TELES.WinRemotePro and Utilities Programs Manual). The default configuration is for PRI Euro ISDN CRC4. To make configuration changes, enter Esc | 0. Type s0stop and press the return key. Use the DOS editor to make the following configuration changes in the file startpbx.bat:
2.5.3.1
PRI Configuration Changes
CRC4 to Double Frame In the following configuration example, /ddd means that all ports are set to double frame. To set a single port to double frame, enter d for the appropriate port (e.g. /d00 means double frame for port 1, /0d0 for port 2, etc.).
Startpbx.bat c:\pabx\s2m3xx.exe /sngl /m:0 /c:32 /ddd 10 d100 IF ERRORLEVEL 1 GOTO ERROR3
TE to NT The following example shows the default configuration.

Startpbx.bat Port TE configured c:\pabx\edss1pte.exe IF ERRORLEVEL 1 GOTO Port NT configured c:\pabx\edss1pnt.exe IF ERRORLEVEL 1 GOTO
32 ERROR3 33 34 /N ERROR3
Pabx.cfg Port TE configured Controller32=9 TES2M DSS1 Port NT configured Controller33=10 NTS2M DSS1
; to network
Euro ISDN to SS7 For a detailed description of SS7 configuration parameters, see SS7-Specific Settings in the Systems Manual for your TELES device.
Page 17
Installation
TELES.iGATE GSM
2.5.3.2
PMP to PP
BRI Configuration Changes
The following example describes how to change the default PMP configuration to PP.
Startpbx.bat c:\pabx\edss1te.exe /PP:0 IF ERRORLEVEL 1 GOTO ERROR3 Pabx.cfg Controller00=20 TE DSS1 PP Controller01=21 NT DSS1 PMP ; to ISDN BRI access ; to network
The entry /PP:<controller> changes the mode from PMP to PP.
2.5.3.3
Configuration of the GSM Interface
After you have connected the antennas and inserted the SIM cards into the SIMcard carriers, insert the SIM card carriers (see 2.8 on page 50) into their appropriate TELES.iLCR 4 GSM Boards. If you are using the TELES.vGATE, SIM-card carriers will not be required (see 2.10 on page 54). The SIM cards will log onto the Status Program with the entry A REG. For detailed information on GSM Status Program entries, see Chapter 2.7. To define PINs for individual SIM cards, edit the subscriber line for the corresponding controller in the pabx.cfg. Example: In the following example, the PIN 1111 is assigned:
Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIM24] CHADDR ALARM
is changed to:
Subscriber00=TRANSPARENT ROUTER GSM[1111,00000,+000000,1,1,1,SIM24] CHADDR ALARM
For detailed information on how to assign PINs, see Chapter 2.6.2.
2.5.3.4
Configuration of the IP Interface
The configuration file for the IP interface is tib.cfg and applies for the TELES.iLCR IP Board and TELES.iLCR VoIP Board. The default configuration is as follows: The IP address includes the IP address and the netmask (in hexadecimal):
OwnLanIpAddress:192.168.0.1:0xffffff00
Page 18
TELES.iGATE GSM
Installation
Network host configuration includes the network address and the netmask (in hexadecimal):
[Host:LocalNetwork] LanIpAddress:192.168.0.0 LanIpMask:0xffffff00 LanIpRouter:local
The default route includes the network address, netmask (in hexadecimal) and the router address:
#[Host:WAN] #LanIpAddress:0.0.0.0 #LanIpMask:0x00000000 #LanIpRouter:192.168.0.10
To activate the default route, remove the # signs and enter the routers address.
2.5.3.5
Configuration of the VoIP Interface
The configuration file for the VoIP interface is tib.cfg. The default configuration is as follows. For a detailed description of the individual entries and possible changes, see Chapter 2.5.3 in the TELES.VoIPGATE Systems Manual:
VOIP:Yes VoipGlobalMaxChan:30 H323OwnIpAddress: VoipRtpPort:29000 H225Port:1720 SipPort:5060 [Voip:iGATE1] VoipDirection:IO VoipIpAddress:192.168.0.0 VoipIpMask:0xffffff00 VoipSignalling:0 VoipCompression:g729 g711a VoipSilenceSuppression:Yes VoipMaxChan:60 VoipTxM:4 #VoipGk:GK1 #[Gatekeeper:GK1] #RasPort:1719 #OwnRasPort:1719 #RasId:VoIPGATE01 #RasPrefix:0049 #GkId:GK #GkAdd:192.168.0.10 #GkPwd: #GkTtl:300 #H323OwnIpAddress:1720 #H323E2EPort:1720 #GkMaxChan:30
To activate the gatekeeper profile, remove the # signs and enter the desired parameters.
Page 19
Installation
TELES.iGATE GSM
2.5.3.6
Remote Access
TELES.WinRemotePro TELES.WinRemotePro remote access can occur via ISDN or IP. The default configuration for ISDN access is set so that the system receives all data calls as remote administration calls. To configure the system so that only certain data calls are received as remote administration calls, make the following changes in the pabx.cfg:
RemoteCode=BBB MapAll4711=BBB DATA
After you have made these changes, you must remove the default entries from the route.cfg as follows:
MapAll0=BBB MapAll1=BBB MapAll2=BBB MapAll3=BBB MapAll4=BBB MapAll5=BBB MapAll6=BBB MapAll7=BBB MapAll8=BBB MapAll9=BBB DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA
For a detailed description of ISDN configuration, see Table 2-2. TELES.WinRemotePro access via IP uses port 4444 as origination TCP port. The following default value (4445) is configured in the tib.cfg file for the systems port:
StatusDPort:4445
The following entry ensures the security of your TELES.WinRemotePro access. Use the Crypt.exe tool to generate the password.
RemotePassword=crypt
HTTP and FTP Remote access can also occur via HTTP or FTP. The following entries in the tib.cfg file ensure the security of your HTTP and FTP access:
Table 2-3 HTTP and FTP Security Parameters Definition Access for HTTP and telnet. Password for full HTTP and telnet access.
Parameter WanUserName:ip WanPassword:ip
Page 20
TELES.iGATE GSM
Installation
Parameter WanROPassword:read WanAllowConfig:Yes FtpUserName:ip FtpPassword:ip FtpROPassword:read FtpAllowConfig:Yes FtpDPort:21 HttpDPort:80
Definition Password for read-only access. Access for IP addresses that are not in the local network. Access for FTP Password for full FTP access. Password for read-only FTP access. Access for IP addresses that are not in the local network. FTP access via the default port. HTTP access via the default port
2.5.3.7
Initial Routing Entries
Routing entries are made in the pabx.cfg and tib.cfg as follows: MapAll<num>=<port><num> Example: MapAll0177=200177 If Chaddr appears in the GSM ports Subscriber lines, the entry will look like this: MapAll<num>=<lain><num> Example: Note: MapAll0177=262030177 Make sure that the numbers for the carriers are routed to the correct ports!
For detailed information on digit collection and enblock/overlap receiving see Chapter 3.1.8.
Page 21
Configuration of the TELES.iLCR 4 GSM Board
TELES.iGATE GSM
2.6
To integrate an additional TELES.iLCR 4 GSM Board into your TELES.iGATE or TELES.iLCR, you must make the corresponding settings in the startpbx.bat and pabx.cfg files. Note: Be sure to save a backup copy of these files before making changes.
2.6.1
Configuration in the startpbx.bat file
To configure the TELES.iLCR 4 GSM Board, enter the new drivers gsmloadt.exe and gsmcardt.exe in the startpbx.bat file as follows:
... c:\pabx\gsmloadt c:\pabx\ ! <card1> ... IF ERRORLEVEL 1 GOTO ERROR ... c:\pabx\gsmcardt /c:<startctrl> <IRQ3> <card1> <IRQ5> <card2>... IF ERRORLEVEL 1 GOTO ERROR ...
Note:
As of Version 5.60b.
If you are using the TELES.iLCR 4 GSM Board in a PRI system, you must also make the following entry in the c:\pabx\s2m3xx.exe... line:
... c:\pabx\s2m3xx.exe ... /gsm:<startctrl> ... ... c:\pabx\nstanl.exe /S0:x+GSM /S2M:y ...
Note:
You must restart the system any time you make changes in startpbx.bat.
Page 22
TELES.iGATE GSM
Optional Parameters The following parameter is optional:

Table 2-4 Optional Parameters in startpbx.bat Parameter /ALT:<main>#<window> Purpose Use this parameter to set the base frequency for the busy signal (<main>) and a frequency window (<windows>). No entry=default. The default setting is: base frequency=400 Hz, frequency window=50 Hz => corresponds with 450 Hz. NOTE: You must configure the parameter /ALT.... after both of the files to be loaded and before the card numbers. No entry = default.
Driver gsmloadt.exe
Page 23
TELES.iGATE GSM
Configuration Example
@ECHO OFF REM REM REM REM REM REM ----------------------------------------------System Type: TELES.iGATE System S2M - 32xGSM Serial Number: VT811111 Software Version: V5.60b Created: Tue Mar 16 11:24:28 2004 -----------------------------------------------
c:\pabx\pbxexist.exe IF ERRORLEVEL 200 GOTO ERROR2 IF ERRORLEVEL 100 GOTO START ECHO The TELES.iLCR/iSWITCH board driver software is already loaded! GOTO OUT :ERROR1 ECHO The TELES.iLCR/iSWITCH board driver software is incomplete! GOTO OUT :ERROR2 ECHO System error in the TELES.iLCR/iSWITCH board driver software! GOTO SYSTEMOUT :ERROR3 IF ERRORLEVEL 250 GOTO ERROR2 IF ERRORLEVEL 243 GOTO ERROR2 IF ERRORLEVEL 230 GOTO ERROR2 IF ERRORLEVEL 222 GOTO ERRORADDR IF ERRORLEVEL 221 GOTO ERRORIRQ IF ERRORLEVEL 220 GOTO ERRORCONF IF ERRORLEVEL 210 GOTO ERRORHARD IF ERRORLEVEL 200 GOTO ERRORVERS IF ERRORLEVEL 191 GOTO ERRORMEM GOTO ERROR2 :ERRORMEM ECHO Insufficient memory for driver software! GOTO SYSTEMOUT :ERRORCONF ECHO The configuration file is missing or incorrect! GOTO SYSTEMOUT :ERRORVERS ECHO Version conflict in the driver software! GOTO SYSTEMOUT :ERRORHARD ECHO The TELES.iLCR/iSWITCH board cannot be accessed! GOTO SYSTEMOUT :ERRORIRQ ECHO The specified interrupt is incorrect! GOTO SYSTEMOUT :ERRORADDR ECHO The specified memory address is incorrect!! :SYSTEMOUT c:\pabx\s0stop.exe CALL c:\backup\startpbx.bat GOTO OUT :START c:\pabx\tsrkrn.exe 64000 /V:5.60b IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\gsmloadt c:\pabx\gsm4isa.bit d800 d900 da00 db00 dc00 dd00 de00 df00 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\iploader d400 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\s2m3xx.exe /sngl /m:0 /c:32 /gsm:0 /PCM2 15 d100 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\iprouter.exe 10 d400 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\hdlc.exe 32 33 34 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\gsmcardt.exe /c:0 7 d8 5 d9 7 da 5 db 7 dc 5 dd 7 de 5 df IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\edss1pte.exe 32 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\edss1pnt.exe 33 34 /N IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\nstanl.exe /S0:8 /S2M:2 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\pabxcfg.exe c:\pabx\pabx.cfg
Page 24
TELES.iGATE GSM
IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\pbxexist.exe IF ERRORLEVEL 100 GOTO ERROR2 ECHO The TELES.iLCR/iSWITCH board driver software is loaded. c:\pabx\status.exe c:\pabx\pabx.cfg :OUT
Note:
When two TELES.iLCR 3PRI Boards are used, only 64 B channels are possible over the PCM highway ribbon cable between the PRI boards. Be sure to set the controllers in the following order: BRI ports, GSM ports, PRI ports, IP port.
2.6.2
Configuration in the pabx.cfg File
The TELES.iLCR 4 GSM Boards GSM channels are configured as additional controllers. Each TELES.iLCR 4 GSM Board contains 4 controllers. The following entries are required:
... Controller<nr1>=<addr> GSM Controller<nr2>=<addr> GSM Controller<nr3>=<addr> GSM Controller<nr4>=<addr> GSM ... Subscriber<nr1>=... GSM[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM24,...].. Subscriber<nr2>=... GSM[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM24,...].. Subscriber<nr3>=... GSM[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM24,...].. Subscriber<nr4>=... GSM[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM24,...].. ...
Page 25
TELES.iGATE GSM
Required Parameters The parameters within the keyword GSM are separated with a comma. The following parameters are required:
Table 2-5 Required Parameters in pabx.cfg Parameter Description <pin> Defines the SIM cards 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 incorrectly 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 centers 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 and 2 or 1, 2, 3 and 4 or 1, 2, 3, 4, 5, 6, 7 and 8 (optional when using the 16 or 32 SIM card carrier (PCMCIA card)). <loudGSM> Defines the volume level to the fixed network. The values 0 to 7 are possible. 7 is loudest and 0 is the least loud. <loudPCM> Defines the volume level to the GSM channel. The values 0 to 3 are possible. 0 is loudest and 3 is the least loud. <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 GSM channels at will.
Page 26
TELES.iGATE GSM
Optional Parameters GSM Specific In addition to the usual LCR optional parameters, you can enter the following optional parameters after the <loudPCM> parameter. Separate each parameter with a comma.
Table 2-6 Optional Parameters in pabx.cfg Parameter Description <busy tone> Enter a value to define the length of the busy signal in ms (default: 500 ms). This value will be used for busy signal recognition. IMSI When you enter this keyword, the IMSIs in each CDR will be recorded. <SIMS> Define this keyword to connect the system to a TELES.vGATE. SIM1 must be defined in the appropriate GSM controller Subscriber line. NOTE: This parameter cannot be used with the following parameters: <SIM24>, <SIMV> and <SIM+>. EXAMPLE:
Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIMS]
<SIMV> Define this keyword to assign a SIM to a GSM controller. The specific SIM (1-24) must also be defined. NOTE: This parameter cannot be used with the following parameters: <SIM24>, <SIMS> and <SIM+>. EXAMPLE:
Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,12,1,1,SIMV]
<SIM+> To use the keyword continue with a SIM-card carrier that is not full, set the parameter SIM+ and define unused SIM-card positions as 0. The system will switch to the first SIM card in the active group after the last one in the SIMcard carrier has been used.
Page 27
Configuration of the TELES.iLCR 4 GSM Board Table 2-6 Optional Parameters in pabx.cfg Parameter Description GSM=...
TELES.iGATE GSM
Enter any of the following parameters after the equal sign for the following functions. All entries must appear in the same line as follows:
GSM=RSSI[10] STOP[18,08] ANNOUNCE[00,08] FAX[a2] ASR[20,35]
RSSI[<limit>] Configure this parameter in front of the interrupts to set a limit for the reception field strength. When the reception field strength falls below this limit, the GSM channel will be blocked. If the field strength is above the limit, the GSM 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. VOICE[1] The B-channel is immediately connected (Siemens dial tone is heard). ALERT Set this parameter in front of the interrupts to generate alert signal in the D channel immediately after dial-end signal. ANNOUNCE Set this parameter to define what happens when a recorded announcement is recognized: No entry (default) A D-channel PROGRESS message stating Inband Information Available will be generated ANNOUNCE[<cause>] The connection will be rejected with the defined cause value. ANNOUNCE[00,<sec>] A timeout for voice recognition is defined in seconds for the TELES.iLCR 4 GSM Board (default value: 120 seconds). After the interval entered has passed, the connection is torn down. FAX[<cause>] This entry allows you to reject fax calls with the defined cause value. STOP[<val1>,<val2>] This entry allows you to define a maximum number of connection setups that always result in a recorded message (<val1>), without a call-connected signal or successful connection setup, or that are always accepted (val2). The GSM 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 default status of this function is off. ASR[<limit>,<calls>] Allows you to change the default value (40 calls at 30% ASR1).
Page 28
TELES.iGATE GSM
Configuration Example
; ################################################# ; System Type: TELES.iLCRD-1PRI ; Software Version: V5.50d ; Created: Thu Feb 21 09:57:57 20021 ; ################################################# ; ================================================= ; FIXED PART, DO NOT CHANGE ; ================================================= ; 1) Hardware ; ----------PABX0=10 d4 S2M PABX1=-- -- GSM PABX2=-- -- GSM PABX3=-- -- GSM PABX4=-- -- GSM PABX5=-- -- GSM PABX6=-- -- GSM PABX7=-- -- GSM PABX8=-- -- GSM PABX9=-- -- VoIP ; 2) HUB board ; -----------BYPASS=ON ; 3) Log-Files ; -----------ActionLog=c:\pabx\protocol.log TraceLog=c:\pabx\trace.log RRUFLOG=c:\pabx\failed.log LogIn=c:\pabx\in.log Log=c:\pabx\cdr.log StatisticTime=c:\pabx\asr.log 00:01 11111111 Rename=c:\pabx\cdr.log &time&.cdr 00:02 11111111 Rename=c:\pabx\failed.log &time&.err 00:03 11111111 Rename=in.log &time&.in 00:04 11111111 ; 4) Configuration-File ; --------------------PermanentFile=c:\pabx\route.cfg ; 5) Controllers ; -------------; TELES.4GSM board(s) ; --------------------Controller00=20 GSM Controller01=20 GSM Controller02=20 GSM Controller03=20 GSM Controller04=20 Controller05=20 Controller06=20 Controller07=20 Controller08=20 Controller09=20 Controller10=20 Controller11=20 Controller12=20 Controller13=20 Controller14=20 Controller15=20 GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM
Page 29
TELES.iGATE GSM
Controller16=20 Controller17=20 Controller18=20 Controller19=20 Controller20=20 Controller21=20 Controller22=20 Controller23=20 Controller24=20 Controller25=20 Controller26=20 Controller27=20 Controller28=20 Controller29=20 Controller30=20 Controller31=20
GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM
; TELES.3PRI board(s) ; --------------------Controller32=9 TES2M DSS1 Controller33=10 NTS2M DSS1 Controller34=11 TES2M DSS1 ; TELES.VoIP board ; --------------------Controller35=40 VoIP Controller36=40 VoIP ; 6) Subscribers ; -------------; TELES.4GSM board(s) ; --------------------Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT Subscriber10=TRANSPARENT Subscriber11=TRANSPARENT Subscriber12=TRANSPARENT Subscriber13=TRANSPARENT Subscriber14=TRANSPARENT Subscriber15=TRANSPARENT Subscriber16=TRANSPARENT Subscriber17=TRANSPARENT Subscriber18=TRANSPARENT Subscriber19=TRANSPARENT Subscriber20=TRANSPARENT Subscriber21=TRANSPARENT Subscriber22=TRANSPARENT Subscriber23=TRANSPARENT Subscriber24=TRANSPARENT Subscriber25=TRANSPARENT Subscriber26=TRANSPARENT Subscriber27=TRANSPARENT Subscriber28=TRANSPARENT Subscriber29=TRANSPARENT Subscriber30=TRANSPARENT Subscriber31=TRANSPARENT
; to public network ; to PBX ; not used
ROUTER GSM[0000,00000,+4917777,1,1,1,SIM24] CHADDR ALARM NEXT ROUTER GSM[0000,00000,+4917777,1,1,1,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,+4917777,1,1,1,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,+4917777,1,1,1,SIM24] CHADDR ALARM ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] GSM[0000,00000,+4917777,1,1,1,SIM24] CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR CHADDR ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM
Page 30
TELES.iGATE GSM
; TELES.3PRI board(s) ; --------------------Subscriber32=DEFAULT Subscriber33=DEFAULT Subscriber34=DEFAULT ; TELES.VoIP board ; --------------------Subscriber35=IP[tib.cfg] ALARM Subscriber36=DEFAULT ; 7) Remote Configuration ; ----------------------RemoteCode=BBB MapAll999=BBB DATA GSM=RSSI[10] STOP[18,08] ANNOUNCE[00,08] FAX[a2] ASR[20,35]
2.6.3
Note:
Customized Configuration for TELES.iGATEs

Changing configuration data and/or SIM-card positions may lead to malfunctions and/or misrouting, as well as possible consequential damage. Make changes at your own risk. TELES is not liable for any damage resulting from or related to such changes. Therefore, please thoroughly check any configuration changes you or a third party have made.
2.6.3.1
Module Distribution of Various Mobile Networks
You can assign each GSM port in the TELES.iGATE system either one mobile network or different access groups to different mobile networks. The port numbers in the TELES.iGATE must be the same for the individual groups. The following configuration samples (from the pabx.cfg configuration file) show the changes:
Page 31
TELES.iGATE GSM
Example 1 All ports in the following example must have the same number for all GSM channels to route calls to the same mobile network. The subscriber line of the first port must also contain the keyword NEXT to ensure the equal distribution of calls.
... Controller00=20 GSM Controller01=20 GSM Controller02=20 GSM Controller03=20 GSM Controller04=20 GSM Controller05=20 GSM Controller06=20 GSM Controller07=20 GSM Controller08=20 GSM Controller09=20 GSM Controller10=20 GSM Controller11=20 GSM Controller12=20 GSM Controller13=20 GSM Controller14=20 GSM Controller15=20 GSM ... Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT Subscriber10=TRANSPARENT Subscriber11=TRANSPARENT Subscriber12=TRANSPARENT Subscriber13=TRANSPARENT Subscriber14=TRANSPARENT Subscriber15=TRANSPARENT ...
ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER
GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24]
ALARM NEXT ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM
Page 32
TELES.iGATE GSM
Example 2 In the following example, a group of 16 GSM channels is assigned to three different mobile networks. The subscriber line of the first port in each group must contain the keyword NEXT to ensure the equal distribution of calls.
... Controller00=20 GSM Controller01=20 GSM Controller02=20 GSM Controller03=20 GSM Controller04=20 GSM Controller05=20 GSM Controller06=22 GSM Controller07=22 GSM Controller08=22 GSM Controller09=22 GSM Controller10=22 GSM Controller11=22 GSM Controller12=24 GSM Controller13=24 GSM Controller14=24 GSM Controller15=24 GSM ... Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT Subscriber10=TRANSPARENT Subscriber11=TRANSPARENT Subscriber12=TRANSPARENT Subscriber13=TRANSPARENT Subscriber14=TRANSPARENT Subscriber15=TRANSPARENT ...
ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER
GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24] GSM[0000,00000,<SMSC>,1,1,1,SIM24]
ALARM NEXT ALARM ALARM ALARM ALARM ALARM ALARM NEXT ALARM ALARM ALARM ALARM ALARM ALARM NEXT ALARM ALARM ALARM
Page 33
TELES.iGATE GSM
2.6.3.2
Network-Specific GSM Routing
Using a Fixed GSM Port Address The customers network routes calls to the mobile network with a defined prefix. Because this code is not always uniform, the TELES.iGATE might have to convert it. Conversion requires the following information: The mobile networks access number Destination number format (with or without prefixes, national or international)
conversion occurs according to the following formula:

<national/international><prefix[incoming]>=<destination number>
converted as:
<port><mobile network access number><destination number>
Be sure to make the following entry in the pabx.cfg configuration file to configure this conversion:
MapAll<nat./int.>prefix[incoming]>=<port><mobile network access number>
The TELES.iGATE or TELES.iLCR system converts national into one zero and international into two zeros. The following configuration exemplifies this conversion as it might occur in Germany:
... MapAll0049172=200172 MapAll0049171=210171 ...
This example shows how the customers network provides the prefix international+49+172+destination number for one mobile network, and international+49+171 for the other. The configuration entries number is converted to see to it that 0049172+destination 200172+destination number and 0049171+destination number is converted to 210171+destination number. The calls to D2 (prefix 0172) are routed to ports with the number 20 and calls to D1 (prefix 0171) are routed to the ports with the number 21. Using the LAIN as the GSM Port Address Use the LAIN as controller with the CHADDR parameter to prevent logging onto the wrong SIM card. This will ensure that routing is network specific.
Page 34
TELES.iGATE GSM
Example:
The following example is based on a German model:

GSM GSM GSM GSM GSM GSM GSM GSM ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER ROUTER GSM[0000,00000,+491722270333,1,1,1,SIM24] GSM[0000,00000,+491722270333,1,1,1,SIM24] GSM[0000,00000,+491722270333,1,1,1,SIM24] GSM[0000,00000,+491722270333,1,1,1,SIM24] GSM[0000,00000,+4917777777,1,1,1,SIM24] GSM[0000,00000,+4917777777,1,1,1,SIM24] GSM[0000,00000,+4917777777,1,1,1,SIM24] GSM[0000,00000,+4917777777,1,1,1,SIM24] CHADDR CHADDR CHADDR CHADDR ALARM ALARM ALARM ALARM
... Controller00=20 Controller01=20 Controller02=20 Controller03=20 Controller04=20 Controller05=20 Controller06=20 Controller07=20 ...
Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT ... MapAll0172=262020172 ... MapAll0177=262030177 ...
CHADDR CHADDR CHADDR CHADDR
ALARM ALARM ALARM ALARM
Note:
If you remove the keyword CHADDR from the pabx.cfg, you must restart the system.
Enter CHADDR[<addr>] to remove a GSM controller belonging to an LAIN group from the standard routing process (e.g. for specific routes or only for SMS transmission). The port address can be set to <addr>. Example:
Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIM24] CHADDR[444] ALARM MapAllSMS=444 05
Page 35
TELES.iGATE GSM
2.6.3.3
Generating and Retrieving CDRs
The following entry in the pabx.cfg configuration file activates the capability to generate CDRs in the TELES.iGATE or TELES.iLCR (for a detailed description of CDR syntax, please see Chapter 2.4.2 of the TELES Infrastructure Systems Parameters and Hardware Manual): Log=c:\pabx\cdr.log The cdr.log file is stored in the c:\pabx directory. New entries are always added to the end of the file. The file is open only during editing. To differentiate between ports with the same number in the CDRs, a specific node number must be defined. You can expand the subscriber configuration line with the keyword NODE[<no.>] for this purpose: Subscriber<xx>=... NODE[<num>] Example:
29.08.01-09:45:24,29.08.01-09:46:33,923456789,[0007:01]01771111111,0101,69,0
In the above formula, <num> consists of a four-digit number that is included in the CDR. Example: The following example shows the pabx.cfg configuration file changed according to the formula:
ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0001] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0002] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0003] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0004] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0005] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0006] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0007] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0008] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0009] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0010] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0011] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0012] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0013] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0014] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0015] ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NODE[0016]
... Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT Subscriber10=TRANSPARENT Subscriber11=TRANSPARENT Subscriber12=TRANSPARENT Subscriber13=TRANSPARENT Subscriber14=TRANSPARENT Subscriber15=TRANSPARENT ...
The CDR contains the IMSI (International Mobile Subscriber Identity), which identifies each subscriber: Example:
08.02.02-09:42:15,08.02.02-09:46:19,912345678,01721111111,111111111111111,0101,244,0
The following example shows the pabx.cfg configuration file changed accord-
Page 36
TELES.iGATE GSM
ing to the formula: Example:

... Subscriber00=TRANSPARENT Subscriber01=TRANSPARENT Subscriber02=TRANSPARENT Subscriber03=TRANSPARENT Subscriber04=TRANSPARENT Subscriber05=TRANSPARENT Subscriber06=TRANSPARENT Subscriber07=TRANSPARENT Subscriber08=TRANSPARENT Subscriber09=TRANSPARENT Subscriber10=TRANSPARENT Subscriber11=TRANSPARENT Subscriber12=TRANSPARENT Subscriber13=TRANSPARENT Subscriber14=TRANSPARENT ... ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM NEXT ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM ROUTER GSM[0000,00000,<SMSC>,1,1,1,IMSI,SIM24] CHADDR ALARM
Note:
If you remove the keyword IMSI from the pabx.cfg, you must restart the system.
You can also rename the file on a monthly, daily or hourly basis so that corresponding data is always readily available in separate files. You can send the files to a specified e-mail account. Enter the following information: Monthly: Rename=cdr.log &time&.cdr 00:00 01. @<account> Daily: Rename=cdr.log &time&.cdr 00:00 11111111 Hourly: Rename=cdr.log &time&.cdr ??:00 11111111 The cdr.log file will by renamed daily or monthly, as yymmddhh.cdr. On April 12, 2002, the file would be renamed as 02041200.cdr. You can retrieve the file by remote administration. Please bear in mind that the customer must maintain the file accordingly, so that the hard disk does not overflow.
2.6.3.4
ASR Calculation and Resetting Statistic Values
When this function is configured in the pabx.cfg file, statistical values, such as the number of minutes, number of calls, ASR, etc., are calculated for the entire system at a defined time. These statistics are then copied into a specified file and reset at 0. This information can also be sent to an e-mail or SMS recipient. The following syntax must be used: StatisticTime=<file> <hh:mm> <day> @<account> Example: In the following example, the systems statistic values are saved daily
Page 37
TELES.iGATE GSM
into the file stati.log and sent to an e-mail account.

StatisticTime=stati.log 00:00 11111111 @<account>
Example:
In the following example, the systems statistic values are saved monthly into the file stati.log and sent to an SMS recipient.
StatisticTime=stati.log 00:00 01. @SMS<mobile number>
Example:
If ?? appears instead of a specified hour, the ASR is written into the stati.log file once every hour. The values are reset to zero in the twenty-third hour:
StatisticTimeReset=stati.log ??:00
Example:
The next example shows how the statistics appear in the file into which they are copied. The following information is listed in the following order: day and time of the entry, followed by the system name. Calls: connected calls followed by the total number of calls in parentheses. The total number of minutes terminated by the system, followed by the ASR1 value, the external ASR for the traffic source (ext) and the internal ASR for the TELES.iGATE (int). These values can differ if a significant number of calls cannot be routed through the TELES.iGATE or an insuffficient number of channels is available for a prefix. Finally, the average call duration (ACD) appears in the entry:
26.10.04-00:00:00,VT810000: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% ASR(ext): 65.12% - ASR(int): 65.30% - ACD: 144.63s
The parameter DeleteCount=On allows you to reset statistic values on the first day of each month and resets count A-H. StatisticTimeReset=<file> <hh:mm> <day> performs the same function as the StatisticTime parameter, but also resets the counters (A-H).
Page 38
TELES.iGATE GSM
Example:
In the following example, the systems statistic values are saved on the 15th of every month into the file reset.log.
StatisticTimeReset=reset.log 00:00 15.
Note:
It is not possible to configure both StatisticTimeReset and StatisticTime. ASR values reset to 0 when the configuration is changed, when the GSM channel is restarted or when the SIM card is changed.
2.6.3.5
Calling Line Identification Restriction (CLIR)
Setting a hash (#) in front of a call number makes it is possible to restrict the identification of calls transmitted into the GSM network. Example: The following example shows an appropriate configuration:
MapIn0049172=#220049172
With this entry, all calls beginning with 0049172 are sent to the port with the address 22 and the identification of the number is restricted.
2.6.3.6
Incoming Voice Calls from GSM
Incoming GSM calls (service indicator 01 represents voice calls) can be routed to a specified number. This enables each GSM controller to receive a unique identifier. It will then be mapped to a number:
Restrict20=90123 01 Restrict21=91234 01
The GSM controllers can also have the same identifier, so that all voice calls (service indicator 01) from controller 20 are sent to number 1111 at port 9. This number could, for example, serve a call center.
Restrict20=91111 01
Changing CLI This function allows you to change the CLI for incoming calls. Bear in mind that the new CLI number is entered in the corresponding log file. In the following entry, the callers CLI <old-cli> to the port with the address <port-addr> is changed to the CLI <new-cli>: Restrict<port-addr><old-cli>=<new-cli> 15
Page 39
TELES.iGATE GSM
It is also possible to change a part of the number, such as the area code: Restrict<port-addr><old-area-code>=<new--area-code> 15 Example: The following configuration example changes the CLI 017201234567 for calls from the port address 26202 to 987654321:
Restrict26202017201234567=987654321 15
The following example changes the area code 0172 for calls from port address 26202 to 0049172:
Restrict262020172=0049172 15
Page 40
TELES.iGATE GSM
2.6.3.7
Setting Time Quotas by Blocking Ports
This 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 immediately or when the call has been terminated; either no more connections will be set up or the system will switch to another SIM 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 GSM channel. To activate this function, enter the keyword LIMIT[<val1>,<val2>,<val3>,<val4>,<val5>,<val6>,<val7> ,<val8>] at subscriber for the corresponding ports SIM card. <valx> defines a number of units as a threshold value for the respective SIM card. If only one limit is entered, this limit will apply for all SIM cards at this port. Note: Make sure you enter the size of the SIM-card carrier (SIM8, SIM16, SIM32) in the Subscriber line.
If a - is entered for <valx>, no limit will apply for the corresponding SIM card. If only two values are entered, a - must be entered for the other SIM cards; these SIMs will have no limit. A corresponding alarm message is generated when the limit on each card has been reached. If the keyword CHANGE is configured, the GSM channel will not switch beyond the second, fourth or eighth SIM card. Different settings are possible for the various SIM-card carriers. The number entered (8, 16, 32) refers to the number of slots. The respective number of SIMs per GSM channel is 2, 4 or 8. The following configurations are possible. Settings shown here are for the SIM32 carrier:
Configuration
LIMIT[10,20,30,40,10,20,3 0,40] CHANGE LIMIT[10] CHANGE LIMIT[10,-,-,-,-,-,-,-] CHANGE LIMIT[10,20,-,-,-,-,-,-] CHANGE
Definition Each SIM card has a defined limit. Each SIM has the same limit. The first SIM has a defined limit, the second has none. SIMs 1 and 2 have defined limits, 3 has no limit.
Note:
In systems running version 5.10k or earlier, the configuration of this keyword causes the GSM channel to switch to the first SIM card after the limit on the last has been reached.
If the keyword CONTINUE is configured, the GSM channel will switch beyond the second, fourth or eighth SIM card. When the limit on the last card has been reached, the GSM channel will switch back to the first card.
Page 41
TELES.iGATE GSM
Note:
All SIM cards must be inserted in the SIM-card carrier for this option to function.
Setting SIM Time Limits In the following example, the GSM channel shuts down when 6,000 intervals of 10 seconds each have passed:
... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000] ...
Setting the Default Time Window In the following example, the GSM channel shuts down when a calculated number of seconds has been reached. If the multiplicator ChargeUnitGenerate=<sec> is configured, the GSM channel will shut down when the value entered in LIMIT multiplied by the value entered here is reached. The default value is 10 seconds. Bear in mind that the value entered in LIMIT may not exceed 65535. In the example, the GSM channel will shut down at 60,000 seconds.
... ChargeUnitGenerate=1 ... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[60000]...
Switching SIMs In the following example, the GSM channel shuts down and switches to the next SIM card when 6,000 intervals of 10 seconds each have passed. The port is blocked after the limit has been reached on the last SIM card:
... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000] CHANGE...
Cyclical SIM Switching In the following example, the GSM channel shuts down and switches to the next SIM card when 6,000 intervals of 10 seconds each have passed. The GSM channel switches to the first SIM card after the limit has been reached on the last SIM card. To reset the counter on a monthly basis, see 2.6.3.4 on page 37:
... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000] CONTINUE...
Page 42
TELES.iGATE GSM
Immediate SIM Switching In the following example, the GSM channel shuts down after the call has been disconnected, and switches to the next SIM card when 6,000 intervals of 10 seconds each have passed. When the parameter LimitWODisc is ON, the call will be torn down when the calling party hangs up. If it is set at OFF, the call will be terminated immediately when the limit is reached:
LimitWODisc=ON ... ...
Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT LIMIT[6000] CHANGE...
Switching SIMs When Carrier is not Full The following example shows how you can use the keyword CONTINUE with a SIM-card carrier that is not full or if specific times are defined for use of individual SIMs (Chapter 2.6.3.10). Set the parameter SIM+ and define unused SIM-card positions as 0. The system will switch to the first SIM card in the active group after the last one in the SIM-card carrier has been used:
NightResetTime=0:00 11111111 ... StatisticTimeReset=23:59 11111111 ... LimitWODisc=ON ... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24,SIM+] LIMIT[6000,6000,0,0,0,0] CONTINUE ALARM NEXT... ...
Setting Start Units The following example shows how you can use the keyword ChargeUnitFirst=<seconds> to configure a starting unit for LIMIT. The following entries are used for SIM card tariffs where the first defined number of seconds are always charged (e.g. the first minute), followed by charges calculated in defined intervals (e.g. every 10 seconds):
... ChargeUnitFirst=60 ChargeUnitGenerate=10 ... Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] LIMIT[6000] ALARM NEXT... ...
Information about the active SIM cards can be found in TELES.WinRemotePro or in the TELES.HTML Configurator and Port Status. To find information about the current counts and limits for each GSM channel, click Statistics. For GSM ports:
Page 43
TELES.iGATE GSM
Count A-H For each GSM channel. Counts are the time slices (from 0 to the limit value) for the individual SIM cards (1-8). When a SIMs set time limit is reached, the channel will disconnect and the next SIM will log on. Click Reset/Set Counters in the Statistics context menu in TELES.WinRemotePro to reset the counters (default value is 0). To reset the counters using the TELES.HTML Configurator, click ResetCount in Port Status. You can also configure the counters to reset automatically (see Chapter 2.6.3.4 on page 37). If LIMIT is configured, bear in mind that SIM 1 must be configured in the pabx.cfg for the corresponding GSM port.
Note:
2.6.3.8
Defining Time Limits for Calls
By entering the parameter CALL in the Subscriber line, you can use LIMIT to terminate calls that reach a defined time limit. For each call the limit is reset at 0. You can define a value anywhere within <limit>-<random>, and you can define a maximum value for <random>. Example:
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 LIMIT[600]
The following entry is required if the TELES.iGATE is used in conjunction with a TELES.vGATE:
Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIM24] CALL[600]
Note:
This LIMIT function cannot be used in conjunction with the LIMIT function described in Chapter 2.6.3.7.
2.6.3.9
Switching SIMs after Each Call
If the parameter NCALL with CONTINUE is entered in the Subscriber line, the SIM will log off after a successful connection and the next SIM will log on. The SIM-card carrier must be full. Example:
Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM24,IMSI] CHADDR NCALL CONTINUE ALARM
Note:
This function cannot be used in conjunction with the LIMIT function described in Chapter 2.6.3.7. Bear in mind that all of the correspond 2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004
Page 44
TELES.iGATE GSM
ing GSM controllers counters must be set at 0.
2.6.3.10 Time-Controlled Configuration

You can define a time at which a GSM channel will change to another SIM card (up to eight SIM cards are possible for this option). The following entries in the configuration file pabx.cfg are necessary:
; 4) Configuration-File ; --------------------PermanentFile=c:\pabx\route.cfg ;Nightfiles ; --------------------NightFile1=c:\pabx\config1.cfg 04:00 11111111 NightFile2=c:\pabx\config2.cfg 05:00 11111111 ... NightFile12=c:\pabx\config3.cfg 16:00 11111111 NightFile19=c:\pabx\config4.cfg 23:00 11111111 NightResetTime=00:00 11111111
A maximum of 19 additional daily configurations are possible (config1.cfg... config19.cfg). The entry NightResetTime reactivates the original configuration. The daymap is read as follows: HoSaFrThWeTuMoSu. Example: The following file is activates Fridays, Wednesdays and Mondays at 12:00 noon unless the day in question is a holiday.
NightFile2=c:\pabx\config2.cfg 12:00 00101010
To generate a NightFile, copy the configuration file pabx.cfg after making the appropriate entries and name it accordingly (e.g. config1.cfg). Finally, enter the SIM-card number (1, 2, optional 1-4 or 1-8) that is to be active during the specified time period in the GSM ports subscriber entry. Example: The following example contains sample entries for individual files.
GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,3,1,1,SIM24] GSM[0000,00000,+491777777,3,1,1,SIM24] GSM[0000,00000,+491777777,3,1,1,SIM24] GSM[0000,00000,+491777777,3,1,1,SIM24]
pabx.cfg: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM NightFile1: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM NightFile2: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM
Page 45
TELES.iGATE GSM
The only difference is in the active SIM card. Activate the configuration after the required files have been copied onto the system. Time-Controlled Logoff of a GSM Channel or SIM Card If a dash (-) is entered in the SIM-card position, the SIM card will log off automatically. Time-controlled activation of configuration files makes it possible to shut off unneeded SIMs, for example at night. Example:
pabx.cfg: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM NightFile1: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM NightFile2: Subscriber12=ALARM Subscriber13=ALARM Subscriber14=ALARM Subscriber15=ALARM GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,1,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,2,1,1,SIM24] GSM[0000,00000,+491777777,-,1,1,SIM24] GSM[0000,00000,+491777777,-,1,1,SIM24] GSM[0000,00000,+491777777,-,1,1,SIM24] GSM[0000,00000,+491777777,-,1,1,SIM24]
2.6.3.11 Checking Ports/GSM Channels

Monitoring ASR for GSM Ports ASR monitoring of the last 40 calls occurs for all GSM ports. If the ASR (ASR1) is lower than 30 percent, an alarm is generated at the corresponding port and the port is blocked. The port is then restarted and a corresponding entry appears in the log file (ASR low). The port is then unblocked. The following entry causes the GSM port to block automatically when this error occurs three times in a row: ASRBlock=On When ASRBlock=Off is used, the port will be restarted and will remain open. The following parameter in the gsmcardt.exe line of the startpbx.bat file allows you to change the default value (40 calls at 30%): ASR[<percent>,<number of calls>] Example:
Subscriber00=ALARM GSM[0000,00000,+00000,1,1,1,SIM24] CHADDR ALARM ASR[20,35]
Page 46
TELES.iGATE GSM
2.6.3.12 Blocking Ports

This function allows you to block a port, so that the corresponding GSM channel is omitted from the distribution of calls. The function is particularly useful when GSM channels fail or SIM cards cannot be immediately replaced. To block a port (i.e. a GSM channel), enter the keyword CHINC[...] in the Subscriber line. In Example 1, port 10 is blocked. Example 1
... Subscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM CHINC[01,01] ...
To activate the port, remove the entry and enter Activate configuration. It is also possible to block an entire port with the remote administration program WinRemotePro. The CHINC[...] function is not necessary with this application. The ports status is displayed by remote administration. You can remove the block with Activate a configuration or with the Unblock option.
Page 47
TELES.iGATE GSM
2.6.3.13 Deactivating Class 2 Re-Routing

Configuring Class2Next=Off in the pabx.cfg file ensures that calls rejected with a class 2 cause value are not re-routed to the next available port.
2.6.3.14 Recharging Pre-Paid SIMs

The routing entry defined here sets up a connection to the network: MapAll<in>=<port>*<cntl>:<num> When the number <in> is dialed, a connection to <num> is set up through <port>*<ctrl>. You can now manually enter DTMF tones using a telephone. To recharge all SIMs in the TELES.iGATE, configure the following mapping in the pabx.cfg, whereby 4400 is an example for the first controller and 12345 is the number for the account manager:
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 MapAll4407=20*0701:12345 MapAll4408=20*0801:12345 MapAll4409=20*0901:12345 MapAll4410=20*1001:12345 MapAll4411=20*1101:12345 MapAll4412=20*1201:12345 MapAll4413=20*1301:12345 MapAll4414=20*1401:12345 MapAll4415=20*1501:12345 MapAll4416=20*1601:12345 MapAll4417=20*1701:12345 MapAll4418=20*1801:12345 MapAll4419=20*1901:12345 MapAll4420=20*2001:12345 MapAll4421=20*2101:12345 MapAll4422=20*2201:12345 MapAll4423=20*2301:12345 MapAll4424=20*2401:12345 MapAll4425=20*2501:12345 MapAll4426=20*2601:12345 MapAll4427=20*2701:12345 MapAll4428=20*2801:12345 MapAll4429=20*2901:12345
For information on recharging SIMs using TELES.WinRemotePro, see Table 1-12 in Chapter 1.6 of the TELES.WinRemotePro and Utilities Programs Manual.
Page 48
TELES.iGATE GSM
GSM Port Status
2.7
GSM Port Status
Various options are available for monitoring the TELES.iLCR 4 GSM Boards status. You can access status information through Alt-F10 in the status program or in the Layer 1 column in the Port Status window in the WinRemotePro program. This data is also recorded in the protocol log. Table 2-7 lists and defines the status entries as they appear in the various programs.
Table 2-7 Status Entries WinRemotePro initialising Status Monitor D INI (blinking red) D SIM (blinking red) D POW (blinking red) D PIN (blinking red) D NOT (blinking red) D... (blinking red) ERR: SIM-Card Protocol Log
Definition GSM channel is in initializing phase
SIM card carrier modnot reg., no sim ule has not been inserted Power supply to the TELES.iLCR 4 GSM Board is not available SIM card could not log on because of incorrectly configured PIN SIM card is logged on, GSM channel is not SIM card is logged on, GSM channel is searching for a base station SIM card is logged on, but barred (e.g. insufficient field strength) SIM card is logged on, GSM channel registers as roaming SIM card is logged on, GSM channel is logged on No SIM card detected or inserted SIM card is logged off, GSM channel is logged off not reg., no power
wrong PIN 1x wrong PIN 2x not reg. sim exists
reg.barred
D BAR (blinking red) D ROA (blinking red) A REG
Barred
roaming
ERR: OK
registered
ERR: OK
no SIM on hold
D sim (blinking red) D (blinking red)
ERR: layer 1 ERR: layer 1
Page 49
The SIM-Card Carrier Module
TELES.iGATE GSM
2.8
The SIM-card carrier module contains the SIM cards for the individual GSM channels. Each TELES.iLCR 4 GSM Board contains one module, which can be inserted into and removed from the back of the TELES.iLCR 4 GSM Board during operation. Depending on the modules specifications and version, up to six SIM cards can be implemented in each GSM channel or you can assign SIMs to individual GSM channels as you wish (see <SIMV> in Table 2-6). SIM cards are mounted on the front and back of the SIM24 module or the front of the SIM4 module (Figure 2-3). 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 modules blue handle, as shown in Figure 2-3. The SIMs on the SIM4 module are numbered from right to left, with one SIM assigned to each GSM channel in ascending order. You can select the SIM cards you would like to use via software.
Figure 2-3 SIM-Card Carrier Modules
SIM0-5
Sim24 Module Front View
10
11
SIM6-11
SIM12-17
Sim24 Module Rear View
12
13
14
15
16
17
18
19
20
21
22
23
SIM18-23
Sim4 Module
Note:
Insert ONLY the SIM-card TELES.iLCR 4 GSM Board!
carrier
module
into
the
Page 50
TELES.iGATE GSM
Entries in the subscriber line of the configuration file pabx.cfg or in nightfiles refer to the SIM positions for each GSM controller. The SIM positions and GSM controllers correspond with the physical SIM slots on the SIM-card carrier module as shown in Table 2-8:
Table 2-8 SIM-Card Positions Slot 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 GSM Controller 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 SIM-Card Position
Page 51
TELES.iLCR 4 GSM Board SIM-Card LEDs
TELES.iGATE GSM
2.9
Table 2-9 contains a description of the LEDs and what they mean: For definitions of settings not described here, see Table 2-9 on page 53.
Ant
Page 52
GSM
The LEDs in the upper column show the general operational status of the SIM cards, while the status of the GSM channels is displayed in the lower column.
GSM Channel 1 GSM Channel 2 GSM Channel 3 GSM Channel 4
Connection Operation LEDs LEDs
SIM
On the spine of the TELES.iLCR 4 GSM Board, to the right of the SIM card module, two columns of green LEDs display the status of each GSM channel.
GSM Channel 1 GSM Channel 2 GSM Channel 3 GSM Channel 4
TELES.iGATE GSM Table 2-9
TELES.iLCR 4 GSM Board LEDs Connection Status Off Definition The GSM channel is not operational because: No external power supply SIM module slot is empty No SIM card Not possible Not possible Not possible The SIM card is attached, but the GSM channel is not operational because: GSM channel is in logon phase GSM channels status is unknown Not possible Not possible The GSM channel is not operational because: SIM card has been blocked Reception field strength below limit Not possible Status during initializing phase (e.g. system start up). Display changes when status of GSM changes. Not possible The GSM channel is operational, the SIM card has logged on. Not possible The GSM channel is operational, the SIM card has logged on, a connection is being set up on this channel The GSM channel is operational, the SIM card has logged on, a connection has been set up on this channel
Operational Status Off
Off Off Off Blinking slowly
Blinking slowly Blinking quickly On Off
Blinking slowly Blinking slowly Blinking quickly
Blinking slowly On Off
Blinking quickly Blinking quickly
Blinking slowly Blinking quickly
Blinking quickly On On On
On Off Blinking slowly Blinking quickly
On
On
Page 53
Connection to a TELES.vGATE
TELES.iGATE GSM
2.10
Connection to a TELES.vGATE
The TELES.vGATE is a system that enables more convenient management of a network of TELES.iGATE systems. All SIM cards in the network are installed in and maintained at a central server, so that it is no longer necessary to install SIM cards into each gateway. The TELES.iGATEs connected to the TELES.vGATE do not require SIM-card carriers, as the TELES.vGATE contains its own SIM-card carriers, which are used for the entire network. Each TELES.iGATE in the network must contain either a TELES.iLCR VoIP Board or a TELES.iLCR IP Board, which provides the connection to the TELES.vGATE. Special drivers (nstanl.exe, pabxcfg.exe and status.exe) for the TELES.vGATE application must also be installed on each connected TELES.iGATE. The following parameters must be configured in the pabx.cfg and the tib.cfg of each TELES.iGATE connected to the TELES.vGATE:
Table 2-10 TELES.iGATE Configuration for Connection to a TELES.vGATE Parameter pabx.cfg SIMS Define this keyword to connect the system to a TELES.vGATE. For detailed information and an example, see Table 2-6 on page 27. Description
tib.cfg SimServer:<mode> SimDBServer:<ip-addr> SimServerBChan:<num> SimServerBCount:<count> SimServerCtrlPing:<sec> Enter Yes to indicate that the TELES.iGATE is attached to a TELES.vGATE. Enter the control units IP address. Enter -1. Used for TELES.iLCR 4 GSM Board Rev. 1.1. Enter the number of TELES.iLCR 4 GSM Boards inserted in the TELES.iGATE. Ping messages (special TCP packets) will be sent to the TELES.vGATE Control Unit in intervals equaling the number of seconds entered. If the TELES.vGATE Control Unit does not respond within 5 seconds, an entry will be generated in the protocol.log file (default 0=disabled).
Page 54
Global System Features
Signaling and Routing Features
The following features apply for one or more TELES Infrastructure Systems. Therefore some of the information in this chapter may not be relevant for your system.
3.1 3.1.1
Signaling and Routing Features Rejecting Data Calls and Specified Speed Dialing
The following configuration enables you to reject calls with bearer capability, data calls and calls that should not be directed to specified numbers:
... MapIn00491721234=&aa VOICE ... MapIn0049172=&aa DATA
3.1.2
Routing CLIP and CLIR Calls
This function allows you to route calls with Calling Line Identification Presentation (CLIP) differently from calls with Calling Line Identification Restriction (CLIR). For example, all CLIP calls can be rejected, so that only calls that do not present the calling number or calls without a calling party number (e.g. analog) are transmitted through the TELES.iGATE. Use the following configuration to define the various routing methods:
... InsertCLIR=On ... Restrict9=OK 01 Restrict|9=OK 01 Restrict90=FAIL 01 ... MapInOK0049172=220049172 MapInFAIL=&aa ...
InsertCLIR=On activates this mode. 01 is the service indicator for telephony (analog and ISDN) and is used to differentiate these calls from remote administration calls. Restrict9=OK 01 means that all telephony calls without a calling number are put through. Restrict|9=OK 01 means that all CLIR telephony calls are put through. Restrict90=FAIL 01 means that all CLIP telephony calls are rejected with No Channel Available as rejection cause when they are mapped to MapInFAIL=&aa.
Page 55
3.1.3
Routing Calls without CLIR
This function enables you to bypass CLIR for calls through the defined port. The following configuration in pabx.cfg activates this function:
Subscriber<xx>=...GSM[...,!CLIR]...
Note:
When this function is configured, the number of the SIM card (and not originating telephone) is transmitted to the B subscriber.
3.1.4
Setting National/International in the Destination Number with DSS1
Enter an n or and i to set a national or international flag in the destination number as follows:
MapAll0039=9i39 VOICE MapAll012=9n12 VOICE
3.1.5
Setting a Default OAD
Use the Restrict command to set a default origination number (*<oad> 15) when the OAD is restricted (<num>): Restrict<port><oad>=*<num> 15 Example:
Restrict9=*12345 15 MapAll030=10030
Use the entry Restrict<port><oad>=<num> 15 if digits at the beginning of the OAD are the only ones to be restricted:
Restrict9004930=030 15 MapAll030=10030
3.1.6
Routing Profiles
Enter Profile<num>=<chan> <minutes> to define up to 10 profiles. If a minus (-) is entered for <chan> or <minutes>, the value will be ignored. When the keyword PROFILE<num> appears in any routing entry, the specified profile will be used for all calls routed using this entry. The value entered in <chan> is the maximum number of channels that can be used simultaneously. The value entered in <minutes> is the cumulative number of minutes the route will be used before it is blocked.
Page 56 2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004
Enter Profile<num>=- -RESET for each profile to unblock ports when the configuration is activated. Example:
; Profiles ; ---------------------PROFILE01=4 PROFILE02=2 PROFILE03=3 PROFILE04=1 Profile01=Profile02=Profile03=Profile04=10 10 5 5 RESET RESET RESET RESET PROFILE01 PROFILE02 PROFILE03 PROFILE04 PROFILE01 PROFILE02 PROFILE03 PROFILE04
MapOut030=913 MapOut031=913 MapOut032=913 MapOut034=913 MapOut035=913 MapOut036=913 MapOut037=913 MapOut038=913
Note:
When one route is blocked, all other routes using the same profile will also be blocked.
3.1.6.1
Limiting Number of B Channels
The parameter MapAl<XX>=<YY> MAX<count> allows you to limit the number of B channels for a specific routing entry. Example: In the following example, customer X may not use more than 10 B channels and customer Y may not use more than 5 B channels in a single PRI connection.
Controller04=9 ... Controller05=80 ... Controller06=81 ... ... Restrict80=XX 01 Restrict81=YY 01 ... MapAllXX=9 MAX10 MapAllYY=9 MAX5 ...
3.1.7
Conversion of Call Numbers
The conversion of call numbers makes it possible, for example, to implement number portability. In the following mapping command, the call number 01720123456 is changed to 01729876543 and sent to the GSM channel (MapAll...=20..):
Page 57
Example 1
... MapAll01720123456=2001729876543
Example 2 presents an alternative, in which the routing file is searched through again after conversion of the call number to determine the route for the prefix 0172. Please bear in mind that you can configure a maximum of 1499 mapping entries with no more than 11 digits in the first part of the command and 19 in the second. Example 2
... MapAll01720123451=$Reception MapAll01720123452=$Reception MapAll01720123453=$Reception MapOutReception=01729876543
3.1.8
Digit Collection (Enblock/Overlap Receiving)
This function makes it possible to collect digits and transmit calls when a specific number of digits has been dialed. The entire call number is required for the call to be set up with a mobile phone or the GSM gateway. Since most numbers have a uniform number of digits, the GSM gateway can collect digits when calls enter the gateway in overlap mode. Digit collection occurs through the following mapping command:
... MapIn0172=|#200172<<14 ... DTMFWaitDial=5 ...
The example above shows a call with the prefix 0172. The 14 at the end is the sum of the port digits and the digits of the called party number (e.g. |#20=3, 01728899666=11, 3+11=14). This figure must be entered in double digits (e.g. <<08 for 8 digits). The parameter DTMFWaitDial defines the amount of time the system waits between the individual digits. The system forwards the call to the GSM channel as soon as the correct number of digits has been dialed. Please bear in mind that you can configure a maximum of 11 digits in the first part of the command and 19 (including a special character, e.g. #) in the second. The call will be forwarded as soon as the specified number of digits has been dialed or a time-out limit has been reached.
3.1.9
Changing Cause Values
It is possible to group cause values together into a single defined cause value so
Functions with the TELES.iLCR IP Board
that rejected calls can be handled in a specified manner by the switch sending the call to the TELES.iGATE. The following cause value groups can be defined in the pabx.cfg: Group 0 Cause Values All connections that are rejected with a group 0 cause value (0x80-0x8f) can be mapped to a single cause value by entering TranslateG0Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form. Group 1 Cause Values All connections that are rejected with a group 1 cause value (0x90-0x9f) can be mapped to a single cause value by entering TranslateG1Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form. Group 2 Cause Values All connections that are rejected with a group 2 cause value (0xa0-0xaf) can be mapped to a single cause value by entering TranslateG2Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form. Group 3 Cause Values All connections that are rejected with a group 3 cause value (0xb0-0xbf) can be mapped to a single cause value by entering TranslateG3Cause=<cau>, whereby <cau> represents a cause value in hexadecimal form.
3.2 3.2.1
Functions with the TELES.iLCR IP Board ftp to the Host via the TELES.iLCR IP Board
With the help of an ordinary ftp program, data can be saved to and retrieved from the TELES.iLCR hard disk. This requires that you are connected with the appropriate TELES.iLCR system via ftp. The transmission format must then be set at binary. Example: ftp <IP address> get charge.log
The following configuration parameters are used for FTP access:

FtpUserName: <name> If it is possible to configure the TELES.iLCR IP Router via FTP, the user name defined here must be used for the configuration.
Page 59
FtpPassword: <password> If it is possible to configure the TELES.iLCR IP Router via FTP, the password defined here must be used for the configuration. FtpROPassword <password> The password entered here must be used for read-only access to the TELES.iLCR IP Router. FtpAllowConfig: <mode> Allows Yes or prohibits <mode> configuration of the TELES.iLCR IP Router via Intranet FTP access. FtpDPort: <num> Enter the number of the port running the ftp server.
Page 60
The following commands can be carried out via FTP access:

Command literal lcr boot literal lcr ipboot literal lcr act literal lcr act 1-19 literal lcr trace 2 literal lcr trace 3 literal lcr trace off Function Boots the entire system Boots the IP router Activates the configuration Activates the NightFile corresponding with the number 1-19 Activates the layer 2 trace Activates the layer 3 trace Deactivates trace
3.2.2
Connection to an SMTP Server
The following entries in the tib.cfg are used to send e-mail messages from the TELES.iLCR, TELES.iGATE or TELES.VoIPGATE. The connection to the SMTP server can be used to send CDR files, alarm messages or incoming SMS to an e-mail account.
MailServer: <mode> Enables (<mode>=yes)or disables (<mode>=no) the Mail Server of the TELES.iLCR IP Router. The server is set at no by default. NOTE: Must be activated during configuration to be written into the configuration file. (Available only with TELES.iLCR system) SmtpServer: <ip addr> In <ip addr>, enter the IP address of the destination SMTP server that is to receive the e-mail messages. (For details see 3.2, Functions with the TELES.iLCR IP Board on page 59). MailRcpt: <domain> In <domain>, enter the destination domain, the destination address and an @ sign. If the destination address is already complete (with an @ sign), <domain> is not added (For details see 3.2, Functions with the TELES.iLCR IP Board on page 59). 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 (For details see 3.2, Functions with the TELES.iLCR IP Board on page 59). MailRcvMax: <count> Length of queue for e-mails that are sent to the LCR
Page 61
MailRcptMax: <count> Number of "RCPT TO" entries in e-mails that come from the LAN (a message is sent to the LCR for each "RCPT TO" entry in each incoming e-mail) MaxMailsToHost: <count> Maximum number of e-mail messages sent to the LCR simultaneously MailToHostDelay: <count> Milliseconds until en e-mail message is sent to the LCR (this timer runs separately for each MaxMailsToHost message) MailToHostRetries: <count> Number of retries when SMS transmission is not successful. When the limit entered is reached, an error message is sent to the e-mail sender (default 3). MailSendMax: <count> Length of the queue for e-mails that are sent to the SMTP server MailSendRetries: <count> Number of times an attempt is made to send an e-mail .
Example:
MailServer:Yes SmtpServer:172.16.0.10 MailRcpt:teles.de MailFrom:172.16.0.100 MailRcvMax:500 MailRcptMax:100 MaxMailsToHost:2 MailToHostDelay:3000 MailSendMax:10 MailSendRetries:10
3.2.3
Sending SMS via E-mail
This function makes it possible to send SMS via a TELES.iGATE with an ordinary e-mail client. SMS messages are recorded in 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 TELES.iGATE must be entered. In the following example, an SMS is sent to the mobile number 01723456789, whereby sms-mail.server.de must correspond with the IP address 172.172.172.172: Example: SMS01723456789@172.172.172.172 or SMS01723456789@sms-mail.server.de
The SMS text must be entered in the text box. The subject box is not used. If the
e-mail program supports sending the same e-mail to more than one address, the SMS messages are sent in intervals of one second. The TELES.iGATEs algorithms evenly distribute the SMS messages to the available ISDN ports or GSM modules. If the TELES.iGATE rejects the call, an e-mail alerting an aborted SMS will be transmitted to the sender and the attempt will be entered in the corresponding log file (RRufLog=). If transmission is successful, a positive response will be sent when the SMS is accepted by the SMS service center. sent will then appear in the subject dialog. A corresponding 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 text to be sent to the TELES.iGATE. All TELES.iGATEs are supported that allow for SMS messages to be sent by the process described above. According to the restrictions of the ISDN signaling protocol, text length is limited to approximately 110-120 characters. Longer texts will be cut off accordingly. The following entry must appear in the pabx.cfg configuration file for SMS transmission to be possible: MapAllSMS=$<port number>.
3.2.4
Receiving SMS Messages
This function makes it possible to receive SMS messages via a GSM gateway with an ordinary e-mail client, to forward them to another mobile telephone, or to save them to a file.
3.2.4.1
SMS to E-Mail
The destination number in the TELES.iLCR system must correspond with an email account. The e-mail recipients name contains the keyword sms and the destination number. The subject box contains the SIM cards IMSI and the callers number. Example: From: sms26202491723230618@gsm.teles.de Subject: SMS 262023203500514 491723230618 The SMS text must be received in a connection setup as a user-to-user message. A mapping entry must indicate an e-mail account with a prefixed @. In the following example, the text is sent to addressee: Example 1 This example applies to the TELES.iGATE or TELES.iLCR with TELES.iLCR 4 GSM Board:
2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004 Page 63
Restrict<port>=@<addressee> 05 Example 2 This example applies to the TELES.iLCR Bridge System with Ecotel Module. Any SMS messages received through the GSM module and forwarded with an ISDN connection setup will be forwarded as email. MapAll<num>=@addressee The recipient can also appear at the beginning of the text. The recipients name must end with # or twice in a row with a colon (:). As an alternative, the @ sign can be substituted with a colon (:) in the recipients address. If only a destination account is given, the configured domain name is used.
3.2.4.2
SMS to SMS
This configuration makes it possible to forward SMS messages via a GSM gateway to another mobile telephone. Restrict<port>=@<port><mobile number> 05
3.2.4.3
SMS to File
Using this configuration, you can save SMS messages via a GSM gateway to a file. Restrict<port>=@FILE:<name> 05
3.2.5
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 supports this service.
Restrict20=@FILE:USSD.TXT 06 Restrict20=@emailaccount 06 Restrict20=91234 06
3.2.6
Sending Messages via E-mail
This function makes it possible to send text messages via the ISDN signaling channel gateway. The destination address with the keyword MSG, the @ sign and the IP address or the IP name of the TELES.iLCR system with GSM gateway must be entered. In the following example, a message is sent to the call number 0123456789,
whereby msg-mail.server.de 172.172.172.172: Example:
must
correspond
with
the
IP
address
MSG0123456789@172.172.172.172 or MSG0123456789@msg-mail.server.de
The message must be entered in the text box. The subject box is not used. If the email program used supports sending the same e-mail to more than one address, the messages are sent in intervals of one second. The TELES.iLCR systems 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 the attempt will be entered in the corresponding log file (RRufLog=). If transmission is successful, a corresponding CDR will be entered with a destination address beginning with MSG. A request to set up a connection with the service telephony and the element user-to-user enables the message to be sent to the recipient. All terminal devices and PBXes are supported that allow for messages to be sent by the process described above. According to the restrictions of the ISDN signaling protocol, text length is limited to approximately 110-120 characters. Longer texts will be cut off accordingly.
3.2.7
Setting Up Connections via E-mail
This function sets up a connection between subscriber A and subscriber B via email. Subscriber A is identified by an 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 IP address or the TELES.iLCR systems IP name. The following example shows a connection with the destination number 0123456789, whereby msg-mail.server.de must correspond with the IP address 172.172.172.172. Example: CALL0123456789@172.172.172.172 or CALL0123456789@msg-mail.server.de
Any text contained in the text box will be sent to subscriber A as user-to-user information. The subject box is not used. Subscriber A is identified by an e-mail address and must be activated in the TELES.iLCR system. The subscribers name must appear before the @ sign. This name must be assigned a corresponding MapOut command. Example: Subscribers e-mail address is meier@server.de. Subscribers extension is 555. Configure MapAll@555=meier.
Page 65
In addition to CTI capability, this function allows for callback via e-mail.
3.2.8
Displaying Incoming Calls
With 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 TELES.iLCR IP Boards subscriber line of the TELES.iLCR systems 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 TELES.iLCR IP Boards subscriber line of the TELES.iLCR systems pabx.cfg configuration file. The destination is the address of the called subscriber configured in a corresponding map entry. A callback can be initiated when the recipient responds to the email.
Page 66
3.2.9 3.2.9.1
Generating Online CDRs Sending CDRs via TCP/IP
CDRs for connected calls and calls for which no connection was set up can be transmitted online to a database. The CDRs can be sent over a TCP connection from the system to the iDB or another application. TCP port 6609 is used, and the system sets up the TCP connection automatically. The following configuration entries are required: In the file pabx.cfg: Log=c:\pabx\charge.log @DB @<ip_address> RRUFLOG=c:\pabx\failed.log @DB @<ip_address> In the file tib.cfg: mailserver:yes The iDB uses the following format for CDR entries, whereby nr represents the number of the CDR, name refers to the name of the system. Individual lines end with LF: S(0,nr,dd.mm.yyyy-hh:mm:ss:lll,0.LCR,nr,name,0) {A(<CDR as generated by TELES.iLCR>)} Example:
S(0,0,04.10.04-13:44:48:000,4,0){ A(04.10.0413:42:44:000){a=20,0101,,,,siap1612345610,,si66610,;c=0,9;n=;p=255;s=edss1;} B(04.10.0413:42:44:000){a=23,0101,,,,siap1612345610,,si66610,;c=0,11;n=;p=255;s=edss1;} C(04.10.0413:42:44:000){a=23,0101,,,,siap1612345610,,si66610,;c=0,11;d=124000;n=;p=255;s=ed ss1;} D(04.10.0413:44:48:000){f=B,CAU_NCC;t=A,CAU_NCC;a=23,0101,,,,siap1612345610,,si66610,;a=20, 0101,,,,siap1612345610,,si66610,;} E(04.10.04-13:44:48:000);
If you use the application cdrd.exe to transfer the online CDRs to a Windowsbased PC, use the command line to call up the tool as follows: cdrd <filename> Two files are generated, whereby one contains the original CDR format and the other contains the iDB format described above. The original CDR entry appears as follows:
04.10.04-13:42:44,04.10.04-13:44:48,1612345610,1111111,0101,124,0
Page 67
3.2.9.2
Sending CDRs via E-Mail
With an appropriate configuration, you can send corresponding CDRs of outgoing and incoming calls as e-mail. The sender is given as cdr and the systems name appears in the subject box. The text box contains the CDR information according to the format for the entry in Log=C:\pabx\charge.log @<account> @<domain>. A space must appear between charge.log and @<account> and between @<account> and @<domain>; @<domain> is optional. You can also send CDR entries via e-mail to an e-mail recipient. Each CDR entry generated is sent as e-mail. The following entry in the configuration file activates this function:
... Log=c:\pabx\charge.log @<e-mail account> @<domain> ...
You can send the entire CDR file to an e-mail account using the following format:
Rename=filename &time&.cdr hh:mm HoSaFrThWeTuMoSu @<e-mail account>
Example:
In the following example, a CDR file is sent every day at 12:00 midnight to the e-mail account entered. The bitmask is HoSaFrThWeTuMoSu, whereby a 1 means the option is active on the corresponding day and a 0 means it is inactive on that day.
Rename=cdr.log &time&.cdr 00:00 11111111 @<email account>
3.2.10
Alarm Notification
3.2.10.1 SNMP Support

The Simple Network Management Protocol facilitates network management and monitoring of TELES.VoIPGATE, TELES.iGATE and TELES.iLCR network devices and their functions. Alarm messages (e.g. Layer 1 errors on E1 lines) and error recovery messages are sent via SNMP trap. Bear in mind that the keyword ALARM must be entered in the appropriate PRI, BRI or GSM ports Subscriber line in the pabx.cfg. The following parameters are used for SNMP configuration:
SnmpD: <mode> Enter yes to activate the SNMP Trap daemon.
Page 68
SnmpTrapServer: <ip addr> Enter the SNMP trap servers IP address. Example for listing more than one: SnmpTrapServer:192.168.0.10 192.168.0.12
It is possible to use TELES-specific management information bases. The following information bases can be used: teles.mib telesigate.mib
3.2.10.2 Sending Alarm Messages via E-mail or SMS

With the appropriate configuration, you can send SMS messages or e-mails containing alarm messages that are written into the log file. The sender is given as alarm and the systems name appears in the subject box. The text box contains the alarm message. Remote administration is sent as CDR. Note: SMS alarms are possible only with TELES.iGATE systems 5.11c or higher.
You can also send alarm messages via e-mail to an e-mail recipient. All alarm messages are sent to the defined e-mail account. The following entry in the configuration file activates this function:
... ActionLog=c:\pabx\prot.log @<e-mail account> ...
Alarm messages can also be sent as SMS messages. The content of the SMS corresponds with the error message. To send SMS instead of e-mail messages, enter the SMS recipients call number, beginning with SMS:
... ActionLog=c:\pabx\protocol.log @SMS01234567890 ...
The following entry ensures that this function becomes active six minutes after starting the system, so that no more than 29 error messages are received after the system is restarted:
MapAllSMS=<port>
Page 69
3.2.11
Automatic Call Generation
With the following configuration in the tib.cfg, you can set up an autodial process that generates incoming traffic via GSM to TELES.iGATE SIM cards that only terminate outgoing calls. SMS can also be sent and received using this function. All values entered here are default values, except where indicated. The integrated TELES.iLCR IP Board initiates these calls and can also receive the same calls:
Table 3-1 Autodial Entry To send calls automatically: AutoDial:Yes AutoDialMaxDuration:60 AutoDialMinDuration:10 AutoDialWait:3600 AutoDialDayMask:127 Activates the service Maximum length of the connection Minimum length of the connection Starts the service 3600 seconds after midnight (default value set at 60 seconds) Daymask: Su | Mo | Tu | We | Th | Fr | Sa 1 | 2 | 4 | 8 | 16 |32 | 64 = 127 The process pauses 60 seconds between calls Enter the number of simultaneous outgoing calls. Enter yes to run the autodial process cyclically at intervals based on the number of seconds configured in AutoDialWait. Default value is no. Enter the number of retries in case of unconnected calls (default 2). Function
AutoDialPause:60 AutoDialSimul:1 AutoDialCyclic:yes
AutoDialRetries:2
To accept the automatic calls through the IP board: Dtmf:Yes DtmfTimeout:70 Activates acceptance Must be greater than the maximum duration (in seconds)
Generating Incoming Calls The numbers that to be called are saved in a file called autodial.cfg which contains entries in the following format: <num> SIM 1 <num> SIM 2
<num> SIM 3 <num> SIM 4 <num> SIM 5 ... <num> SIM n Example:
01721111111 01721111112 01721111113 01721111114 01721111115 01721111116 01721111117 01721111118 01721111119 01721111110
The following configurations must be entered in the pabx.cfg: For the transmitted call:
MapOut 0172=200172
For the incoming call (the calls for the corresponding GSM ports must be connected to the IP board):
Restrict20=<IP port>DTMF
Note:
The autodial process restarts when the TELES.iGATEs configuration is activated.
Generating SMS To generate automatic SMS transmission and reception, place an entry in the autodial.cfg file, beginning with SMS, followed by the destination number and text. The entry should appear in the following syntax: SMS<num> TEXT An SMS containing the message TEXT is sent to the defined number. Example:
SMS01721111111 AutodialSMS01 SMS01721111112 AutodialSMS02 SMS01721111113 AutodialSMS03
The following entry must appear in the pabx.cfg:

MapAllSMS=<port>
Page 71
If the keyword CHADDR is also used, enter <LAIN> instead of <port>:

MapAllSMS=<LAIN>
Make the following additional entry if the SMS is to be sent to a SIM card that is in the same system as the SIM card sending the SMS:
Restrict<port>=@FILE:<name> 05
Page 72
3.2.12
Setting the Systems Clock with SNTP
If the TELES.iGATE only handles incoming traffic, its clock is not set through the telephony network. Simple Network Time Protocol (SNTP) enables the TELES.iGATE to set its own clock automatically. This is also useful during changes from Summer to Winter Time and vice versa. To configure SNTP, you must enter the following parameters in the tib.cfgfile: Note: If the system is connected via BRI or PRI, a clock may come from the network connected to the corresponding port. Enter !TIME in the pabx.cfgs subscriber line and then activate the configuration to block this clock.
SntpClient: <mode> Enter yes to activate Simple Network Time Protocol. SntpServer: <ip addr> Enter the IP address of the SNTP server. SntpInterval: <hour> Enter an interval (in hours) for time queries. SntpTzadaption <sec> Enter an amount of time in seconds to adjust a time zone. Every time a new time is set, the system will then adjust the time by adding or subtracting the number of seconds entered. For example, if a system in Paris takes Greenwich Mean Time, it will add an hour if this parameter is set at 3600 seconds. To subtract, enter a minus (-) in front of the seconds. SntpDaylightSaving: <format> Use this parameter to define daylight savings time. The following formats are possible: Euro The data for Europe is automatically used. !Euro European data is inverted for use in the southern hemisphere. mmtthh:mmtthh For other regions, enter the starting and ending times for daylight savings time. SntpVersion: <num> Use this parameter to define the version of the SNTP server. 3 or 4 are possible. The default value is 4.
Page 73
3.2.13
DTMF Tone Detection and Call Setup
The TELES.iLCR IP Board enables the TELES.iLCR to recognize DTMF tones and to initiate calls from these tones. You can use the TELES.HTML Configurator or the configuration file tib.cfg to activate the DTMF server on the TELES.iLCR IP Board. Using the TELES.HTML Configurator To access the DTMF servers HTML page, click Configuration | System | DTMF Server. Activate the server, confirm activation and save the new configuration. Using the Configuration File tib.cfg Enter DTMF:YES in the system parameters. Note: The IP router must be restarted to activate this configuration.
DLA with DTMF Make the following entries in pabx.cfg to connect a call directly: MapAll<number>=<IPport>DTMF MapAllDLA=<port> Example: In the following example, the call from the number 123 is connected and the call that comes in as DTMF tones is directed to port 9:
MapAll123=<ip port>DTMF123 MapAll321=<ip port>DTMF321
Callback with DTMF and Pre-configured Callback Number Make the following entries in pabx.cfg to initiate callback to a fixed number: MapAllDTMF=<IPport>DTMF MapAllDLA=<port> MapAll<number>=CALL<callbacknumber> Example: In the following example, the call with the number 123 is connected with the number 03012345. The number that comes in as DTMF is directed to port 9:
MapAllDTMF=40DTMF MAPAllDLA=9 MapAll123=CALL903012345
Note:
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 en 2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004
Page 74
try recording the A subscribers connection time is generated in the rr.log file. Callback with DTMF and OAD as Callback Number The following entries in pabx.cfg will initiate callback to the calling partys number: MapAllDTMF=<IPport>DTMF MapAllDLA=<port> MapAll<number>=CALLB MapAllCB=<port> Example: In the following example, the call with the number 123 is connected with the OAD and the number that comes in as DTMF is directed to port 9:
MapAllDTMF=40DTMF MapAllDLA=9 MapAll123=CALLB MapAllCB=9
Using a PIN in Front of the Actual Call Number To prevent abuse, the following entry can be made to configure a PIN in front of the actual call number: MapAllDLA=$PIN MapAllPIN<pin>=<port> Example: In the following example, the DTMF tones are analyzed, whereby the first 4 (1111) corresponds with the PIN. The call to subscriber B is initiated when the PIN has been entered correctly. All other DTMF tones are directed to port 9:
MapAllDLA=$PIN MapAllPIN1111=9
Special Announcements for Specific Called-Party Numbers Various announcements can be played for specified called-party numbers. The following entries are required to activate this option: Example: In the pabx.cfg file:
MapAll123=<ip port>DTMF123 MapAll321=<ip port>DTMF321
In the tib.cfg file:

DtmfAnnounce:123 voice1.711 321 voice2.711
Page 75
In this example, voice message voice1.711 will be played when the number 123 is called and voice message voice2.711 will be played for the called number 321. Make the following entry in the pabx.cfg file if the same announcement is to be played for all incoming calls:
MapAll123=<ip port>DTMF
Bear in mind that the announcements filename must be DTMF.711.
3.2.14
Callback via HTML
If your TELES.System has an integrated TELES.iLCR IP Board or TELES.iLCR VoIP Board, callback calls can be initiated using the systems HTML interface. The following implementation scenarios are possible: Call setup with a fixed first and fixed second leg Call setup with a fixed first leg Call setup with configurable call numbers These scenarios can also be mixed. To set up callback via HTML, you must first set up a callback.cfg file on the system. Individual user accounts are defined in this file as follows: user1 password1 <first leg number> <second leg number> user2 password2 <first leg number> user3 password3 Example 1 The following example is of a callback.cfg with a fixed first and second leg:
oma abcd 9123456 9654321 opa efgh 9456789 9654321 papa ijkl 9321987 9654321
Example 2 The following example is of a callback.cfg with a fixed first leg:

oma abcd 9123456 opa efgh 9456789 papa ijkl 9321987
Example 3 The following example is of a callback.cfg with a configurable call number:
Page 76
oma abcd opa efgh papa ijkl
The following routing entries in the pabx.cfg are also required. The first entry is for the callback and the second is for the destination number: MapAllCB=<port> VOICE MapAllDLA=<port> VOICE Example: In the following example, both legs are set up through the PRI line of controller 9:
MapAllCB=9 VOICE MapAllDLA=9 VOICE
To use this feature as a user, you must log on the system with the defined user name and password. The user page appears, along with possible settings configured in the callback.cfg. After successfully entering the destination numbers and clicking OK, the call is set up and Callback has been initiated appears. The first leg is then set up, followed by the second leg.
Page 77
Number Portability and Black and White Lists
3.3 3.3.1
Number Portability and Black and White Lists Activation License
A license is required to use number portability and black and white list databases on the system. The license is based on the hardware serial number (ID) for the first PRI board in the system. You can display the serial number by running the program hw3xx.exe for the first PRI board or using TELES.WinRemotePro: hw3xx.exe hw3xx <Address> <Interrupt> [ID: PMxxxxxx] is displayed. Example:
hw3xx d100 10 Teles.3S2M: Hardware -Test V5.30f [Addr: d100- IRQ: 10] [ID: PM903708]
TELES.WinRemotePro In the Port Status window, right-click the appropriate port and select Layer 1 Statistics for this Port. The serial number appears at the bottom of the window.
Attach the license number to the entry for the first PRI board in the Hardware field of the pabx.cfg configuration file (XXXXXXXX in the following example. YYYYYYYY represents the optional SS7 license).
; 1) Hardware ; ----------... PABX0=10 d1 S2M YYYYYYYY XXXXXXXX ...
Please be sure and check that the Interrupt (10 in the example) and I/O Address (d100 in the example) are the values you use in startpbx.bat. Write the li-
Page 78
cense number in upper case letters only. Note: You must restart the system after entering the license number. To ensure that your license is active, check the General view in TELES.WinRemotePro. NP will appear in the first line behind System Type as shown below if the license is active:
Page 79
3.3.2
Number Portability
Ported Number LCR Extension is a function that enables you to map defined destination call numbers to other destination numbers or networks (Number Portability). This function is used to allow telecommunications subscribers to 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 mapped in their respective networks. Implementation of this information and the corresponding routing processes result in significant cost savings, as tariff differences between calls to normal and ported subscribers are eliminated.
3.3.2.1
System Requirements
TELES.iGATE, TELES.iLCR and TELES.iACCESS systems running version 5.11 or higher support Ported Number LCR Extension. This function is optional and requires a license number for activation. As a stand-alone option, TELES.iGATE systems offer the greatest cost savings for termination of mobile traffic. The following system requirements must be fulfilled to set up and activate Number Portability: A 486 processor or newer, 100 MHz or higher Version 5.11 or higher A valid license number for Number Portability Available hard disk space, depending on the size of the database Database file(s) corresponding to the specifications defined in Chapter 3.3.2.2.
3.3.2.2
Database
A binary search algorithm is used to search the database, so that a database containing 1,000,000 elements requires no more than 20 searches. This optimized search process requires that all elements in the database are sorted in ascending order. On average, the database search occurs within 250 ms. The total process results in a maximum delay of 1 second (500 ms on average). The database presented here consists of one file (ASC-II) and is subject to the following restrictions: 1st line in the file The file's first line always contains the field length and the number of database el-
Page 80
ements. This line must be 20 bytes long. The field length begins at position 0, the number of elements at position 4. 2nd to nth line in the file Lines 2 to n contain the database elements. Each element must have the field length defined in line 1. Bear in mind that carriage return/line feed each count as one byte in the field length. All elements must be sorted in ascending order. Database elements Each database element contains the destination number to be verified, followed by a separator (colons, spaces and commas are allowed) and the new destination number to be used. The new destination number ends with the last valid digit (i.e. 0 9), or an asterisk can follow the last digit if the verified number should be added to the new number (instead of replacing it). File names The name of the database file must begin with a D and end with db. The file's name must conform to the 8.3 rule (the name of the databank can have no more than 8 characters). The carrier prefix must be encoded in the name, so that the database file can be divided into several (possibly smaller). Note: The database file may not exceed 200 Mbytes. This feature has been successfully tested using a database with up to 1,000,000 entries.
3.3.2.3
Routing and Configuration
A D or an N appears as routing information in front of the actual carrier prefix in the configuration. This configuration enables targeted routing, depending on whether or not the numbers appear in the database. A D means that the destination number is not in the database. An N signifies that the number is in the database and the call is routed accordingly. An appropriate routing entry in the pabx.cfg file is required to activate Ported Number LCR Extension. This includes activation of digit collection and the following mapping configuration:
DTMFWaitDial=<sec> MapIn<in>=|D<area><<<count> MapAllD<area>=<port><area> MapAllN<area>=<port><area>
Page 81
Note:
A corresponding database file named D<area>.db is also required.
Example 1 The following entry in the configuration file pabx.cfg is required for 11-digit numbers with carrier prefix 0172. Ported calls are routed to their corresponding network providers:
DTMFWaitDial=5; maximum wait in seconds MapIn0172=|D0172<<12; 12 = number of digits (11) + D MapAllD0172=262020172 MapAllN26201=26201 MapAllN26203=26203
The following database file, D0172.db, contains ten entries that ensure that the call is routed accordingly:
20 10 01720000000:26203* 01721111111:26201* 01722222222:26201* 01723333333:26203* 01724444444:26201* 01725555555:26203* 01726666666:26203* 01727777777:26203* 01728888888:26201* 01729999999:26201*
The corresponding numbers are then routed accordingly to 26201 (e.g. 01721111111, 01724444444 etc.) or to 26203 (e.g. 01727777777, 01723333333 etc.). Example 2 With the following configuration, the ported calls in Example 1 will be rejected with the cause value No Channel Available (0xa2) (888888 is a random, unassigned number):
DTMFWaitDial=5; maximum wait in seconds MapIn0172=|D0172<<12; 12 = number of digits (11) + D MapAllD0172=262020172 MapAllN888888=&a2
Page 82
The database file for this configuration will look like this:
20 10 01720000000:888888 01721111111:888888 01722222222:888888 01723333333:888888 01724444444:888888 01725555555:888888 01726666666:888888 01727777777:888888 01728888888:888888 01729999999:888888
3.3.3
Black and White Lists
A black or white list can be configured using the same database structure and files used for Number Portability. The system searches the database for calling party numbers and, depending on the configuration, routes or rejects the calls accordingly. To activate this function, follow the same steps used for Number Portability (see Chapter 3.3 on page 3-78), using a lower-case d instead of an upper-case D, and make the following entry in the configuration file pabx.cfg: Example 1 Black list
;Black List ;-----------------Restrict10=BL MapAllBL=|d222<<11 MapAlld222=<port> MapAllN8888888=&a2
20 10 22200000000:888888 22211111111:888888 22222222222:888888 22233333333:888888 22244444444:888888 22255555555:888888 22266666666:888888 22277777777:888888 22288888888:888888 22299999999:888888
Example 2 White list

;White List ;-------------------Restrict10=WL MapAllWL=|d222<<04 MapAlld222=&a2 MapAllN555WL=9
Page 83
17 10 2220000000:555* 2221111111:555* 2222222222:555* 2223333333:555* 2224444444:555* 2225555555:555* 2226666666:555* 2227777777:555* 2228888888:555* 2229999999:555*
Page 84
SS7-Specific Settings
3.4
As of Version 4.0, TELES.iLCR supports the SS7 protocol for internal communication between switches on the corporate network. As a result, the Layer 2 and 3 drivers have been replaced. The ss7_isup.exe driver has been added for Layer 4. To make use of SS7 support, replace references to hdlc.exe with ss7_l2.exe and substitute ss7_l3.exe for edss1...exe for each of the appropriate ports in the STARTPBX.BAT file. In each case, the port number is added as a parameter. If SS7 and DSS1 ports are both configured, make sure that the hdlc.exe and edss1...exe drivers are started AFTER the SS7 ports. See the example on the right for typical syntax:
... :START c:\pabx\tsrkrnx.exe 64000 /V:5.30f c:\pabx\s2m3xx.exe 10 d400 /c:4 /m:0 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\pabx.exe 15 d100 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\ss7_l2.exe 4 5 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\ss7_l3.exe 4 5 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\ss7_isup.exe 4 5 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\hdlc.exe 0 1 2 3 6 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\edss1pnt.exe 6 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\edss1te.exe /PP:0 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\edss1nt.exe 1 2 3 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\nstanl.exe /S0:1 /S2M:1 IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\pabxcfg.exe c:\pabx\pabx.cfg IF ERRORLEVEL 1 GOTO ERROR3 c:\pabx\pbxexist.exe IF ERRORLEVEL 100 GOTO ERROR2 ECHO The driver software of the TELES.PBX board has been loaded. c:\pabx\status.exe c:\pabx\pabx.cfg :OUT
Note:
The optional keyword FIS in the line c:\pabx\ss7_L2.exe/FIS 4 5 causes an increase in FISU messages for controllers 4 and 5. To avoid a high volume of D-channel traffic on these controllers, use this keyword only if necessary.
Page 85
Add an SS7-specific mapping for each port on which you intend to run this protocol. Map the port number (followed by a zero) to the same number (i.e. MapOut90=90). The following adjustments must also be made to the Controller Subscriber commands in the PABX.CFG: and
1. For each of the SS7 ports, add the SS7 keyword to the Controller command after TES2M or NTS2M. 2. Using the Subscriber command, configure the SS7 ports using the following keywords: SubscriberPort=SS7[OPC,DPC,SSV,SLC,CIC, type] The point codes (OPC,DPC) can appear in hexadecimal values or in the following format: 4 bit-3 bit-4 bit-3 bit. All other values are hexadecimal, with a leading zero, but no leading format identifier 0x.
Keyword OPC DPC Meaning Own Point Code: distinctly identifies the port within the corporate network. Use a different four-digit hexadecimal value for each port. Destination Point Code: used to distinctly identify the target port within the corporate network. Specify a four-digit hexadecimal number for each port. Subservice for the target port: 80 for national port on the corporate network (NAT0) 00 for international port on a foreign network C0 for test (NAT1) Signaling Link Code: used to distinctly identify the lines running in the same direction on Layer 3. Specify a hex value from 00 to 0F. Circuit Identification Code: used to identify B channels to the remote switch. Specify a four-digit hexadecimal number. Trunk standard line (no signaling) LINK for standard usage and signaling in one line For each connection, at least one LINK must be configured in correspondence with the configuration used by the remote switch.
SSV
SLC CIC type
Page 86
The diagram below shows four switches communicating via SS7:

OPC
DPC 4
DPC 2 DPC 3
Controller 04 OPC
SLC 1 SLC 2 SLC 3
80 national
Controller 05
OPC
Trunk Trunk Link&Trunk
00 international
OPC
Table 3-2
Sample of pabx.cfg
; 5) Controllers ; -------------; TELES.3PRI board(s) ; --------------------Controller00=20 NT DSS1 Controller01=21 NT DSS1 Controller02=22 NT DSS1 Controller03=23 NT DSS1 Controller04=9 TES2M SS7 Controller05=9 TES2M SS7 Controller06=10 NTS2M DSS1 ; 6) Subscribers ; -------------; TELES.3PRI board(s) ; --------------------Subscriber04=SS7[1-7-a-3,1-7-a-1,80,00,0000,LINK] TRANSPARENT Subscriber05=SS7[1-7-a-3,1-7-a-1,80,01,0020,LINK] TRANSPARENT Subscriber06=TRANSPARENT ROUTER ; 7) Remote Configuration ; ----------------------RemoteCode=999 MapOut0=90 MapOut1=91 MapOut2=92 MapOut3=93 MapOut4=94 MapOut5=95 MapOut6=96 MapOut7=97 MapOut8=98 MapOut9=99 MapIn1=101
3.4.1
Activation License for the SS7 Protocol
A license is required to use the SS7 protocol on the system. The license is based on the hardware serial number (ID) for the PRI boards in the system. You can display the serial number by running the program hw3xx.exe for each PRI board or using TELES.WinRemotePro:
Page 87
hw3xx.exe hw3xx <Address> <Interrupt> [ID: PMxxxxxx] is displayed. Example:

hw3xx d100 10 Teles.3S2M: Hardware -Test V5.30f [Addr: d100- IRQ: 10] [ID: PM903708]
TELES.WinRemotePro In the Port Status window, right-click the appropriate port and select Layer 1 Statistics for this Port. The serial number appears at the bottom of the window.
Attach the license number to the entry for each PRI board in the Hardware field of the pabx.cfg configuration file (YYYYYYYY in the following example. XXXXXXXX represents the optional number portability license).
; 1) Hardware ; ----------... PABX0=10 d1 S2M YYYYYYYY XXXXXXXX ...
Please be sure and check that the Interrupt (10 in the example) and I/O Address (d100 in the example) are the values you use in startpbx.bat. Write the license number in upper case letters only. Note: You must restart the system after entering the license number. To ensure that your license is active, check the General view in TELES.WinRemotePro. SS7 will appear in the first line behind System Type as shown below if the license is active:
Page 88
Support of SS7 Level 3 Maintenance Functions TELES.WinRemotePro allows you to query SS7 Level 3 status information and perform the following commands: Inhibit Link Uninhibit Link Activate Link Deactivate Link Activate Linkset Deactivate Linkset These functions are specifically for testing SS7 signaling routes.
Note:
Support of Other SS7 ISUP Maintenance Functions TELES.WinRemotePro allows you to perform the following SS7 ISUP maintenance functions: Circuit Group Reset (restarts port) Circuit Group Block (blocks port) Circuit Group Unblock (unblocks port) Reset Circuit (mask-dependent channel reset) Block Circuit (mask-dependent channel block) Unblock Circuit (mask-dependent channel unblock) These functions are specifically for testing SS7 signaling routes.
Note:
For more information on the uses and applications for TELES.WinRemotePro, see Chapter 1 of the TELES.WinRemotePro and Utilities Programs Manual.
Page 89

TELES iGATE v4 9

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TELES iGATE v4 9

Uploaded by

Copyright:

Available Formats

TELES.

iGATE Systems Manual

TELES.iGATE GSM ....................................................................... 6

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

3 Global System Features ................................................................55

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Safety and Security Precautions

Safety and Security Precautions

Tips for EMC Protection

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Servicing the System

Safety and Security Precautions

Servicing the System

Replace components according to the following table:

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Protecting the Operating System

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Safety and Security Precautions

The firewall must support the following features:

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Safety and Security Precautions

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

How TELES.iGATE Works

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Supported Implementation Scenarios

Supported Implementation Scenarios

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Supported Implementation Scenarios

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Supported Implementation Scenarios

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

TELES.iGATE Hardware Installation

TELES.iGATE for 4-32 GSM Channels: Rear View

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Table 2-1 describes the numbered arrows shown in Figure 2-1.

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

TELES.iGATE VoIP for 4-60 GSM Channels: Rear View

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Table 2-2 describes the numbered arrows shown in Figure 2-2.

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Basic Configuration of the TELES.iGATE

PRI Configuration Changes

TE to NT The following example shows the default configuration.

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

BRI Configuration Changes

The entry /PP:<controller> changes the mode from PMP to PP.

Configuration of the GSM Interface

Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIM24] CHADDR ALARM

For detailed information on how to assign PINs, see Chapter 2.6.2.

Configuration of the IP Interface

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Configuration of the VoIP Interface

2004 by TELES AG Berlin, Version 4.8/SH-e/10.26, Issue: October 2004

Parameter WanUserName:ip WanPassword:ip

2004 by TELES AG Berlin, Version 4.8/SH-e/05.02, Issue: October 2004

Parameter WanROPassword:read WanAllowConfig:Yes FtpUserName:ip FtpPassword:ip FtpROPassword:read FtpAllowConfig:Yes FtpDPort:21 HttpDPort:80

Initial Routing Entries