Teles Informationstechnologien CDMA32VOIPUS Cellular/PCS CDMA Gateway User Manual TELES iGATE V16 2

Teles AG Informationstechnologien Cellular/PCS CDMA Gateway TELES iGATE V16 2

UserManual.wiki >

Teles Informationstechnologien >

CDMA32VOIPUS User Manual

Users Manual

CELLXReference ManualSoftware version 16.2

TELES AG | HEADQUARTERSErnst-Reuter-Platz 810587 BerlinGERMANYPhone +49 30 399 28-066Fax +49 30 399 28-051E-mail sales@teles.comhttp www.teles.com© Copyright 2010 TELES AG Informationstechnologien. All rights reserved. TELES®, IntraSTAR®, Intra*®, iGATE®, and iSWITCH® are registered trademarks of TELES AG Informationstechnologien. All other trademarks used are the property of their respective owners.The supplied hardware/software systems are protected by copyright and can be used solely by their lawful owners.All text and figures in this publication have been compiled with great attention to detail. Nonetheless, inaccuracies and typographical errors cannot be entirely avoided. TELES AG Informationstechnologien provides this document 'as is' without warranty of any kind, expressed or implied. TELES AG Informationstechnologien reserves the right to make changes in product design or specifications without notice.Reference ManualCELLXCELLX 16.2Revised:18 November 2011Software version: 16.2

Page 1CELLX 16.21 About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.2 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.3 Safety symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Safety and security precautions . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Safety measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.2 FCC / Industry Canada Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.3 EMC protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.4 System security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.5 Servicing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.5.1 Replacing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122.5.2 Protecting the operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122.6 CDR files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.7 Network security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 What’s new in version 16.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.2 New Access Gateway product names starting version 16.1 . . . . . . . . . . . . . . . . . . .163.3 How CELLX works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173.4 Supported implementation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1 Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204.2 Package contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204.3 Hardware description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204.4 Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214.4.1 Ethernet wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214.4.2 PRI wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.4.2.1 TELES to TBR12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.4.3 Antenna connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.4.4 SIM card assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.5 Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.6 Hardware connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.7 Startup with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.7.1 Installing Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.7.2 Configuration with Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264.8 Startup via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284.9 LED functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294.9.1 Ethernet port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294.9.2 Base Board PRI port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294.9.3 Mobile Board SIM card LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294.10 Remote access and access security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.10.1 GATE Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.10.2 Graphical user interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324.10.3 FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334.10.4 Setting a password for remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Page 2CELLX 16.25 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.1 Configuration file ip.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385.1.1 System section configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385.1.2 Ethernet interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395.1.3 GUI settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395.1.4 Bridge configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405.1.5 NAT configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405.1.6 PPPoE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415.1.7 Firewall settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425.1.8 Bandwidth control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445.1.9 DHCP server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465.1.10 DNSmasq settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .475.1.11 PPP configuration for mobile and ISDN dial-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . .485.1.12 VLAN configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .495.1.13 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .505.1.13.1 Default configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .505.1.13.2 Active ethernet bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .505.1.13.3 Integrated DSL-router scenario for VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515.1.13.4 VLAN scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.2 Configuration file pabx.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.2.1 System settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.2.1.1 Global Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.2.1.2 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535.2.1.3 Night configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555.2.1.4 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .565.2.1.5 Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595.2.1.6 Global settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .625.2.2 SMTP-client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .655.2.3 Number portability settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .675.2.4 SNMP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .685.2.5 Time-controlled configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .685.2.6 .CASR2 settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .685.3 Configuration file route.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705.3.1 Entries in the [System] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705.3.1.1 Restrict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705.3.1.2 MapAll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .725.3.1.3 Redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .745.3.1.4 Setting the time-controlled sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .755.3.2 VoIP profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765.3.3 Gatekeeper profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .795.3.4 Registrar profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .805.3.5 Radius profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .816 Routing examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.1 CELLX integration in an H.323 carrier network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .846.2 CELLX as a second-generation LCR with VoIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .857 Mobile configuration options . . . . . . . . . . . . . . . . . . . . . . . . . 877.1 Network-specific mobile routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .887.1.1 Routing decisions for calls to the mobile network . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Page 3CELLX 16.27.1.2 Using the LAIN as the mobile port address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .897.1.3 Fixed LAIN for a mobile port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .907.2 Incoming voice calls from mobile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .907.3 Blocking ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .907.4 Mobile user PBX callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .917.5 Optional mobile quality parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .927.6 Deactivating mobile rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .957.7 Setting autodial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .967.8 Disconnecting calls after ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .967.9 Checking ports/mobile channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .967.10 Defining special characters for voice calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .978 Signaling and routing features . . . . . . . . . . . . . . . . . . . . . . . . 988.1 Least cost routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998.1.1 Carrier selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998.1.1.1 Routing entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998.1.2 Alternative routing settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1008.1.3 Charge models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1018.2 Online traffic monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1028.2.1 ASR calculation and resetting statistic values and counters. . . . . . . . . . . . . . . . . . .1028.2.1.1 Saving and sending statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1038.2.1.2 Saving statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1048.2.1.3 Resetting statistic counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1048.2.2 Generating and retrieving CDRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1058.2.2.1 Call log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1068.2.2.2 Missed calls list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1118.2.2.3 Sending CDRs via e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1128.3 Ported number screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1138.4 Digit collection (enblock/overlap receiving) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1148.5 Rejecting data calls and specified numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1158.5.1 Blacklist routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1158.5.2 Whitelist routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1158.5.3 Rejecting calls with ISDN bearer capability data. . . . . . . . . . . . . . . . . . . . . . . . . . . .1168.5.4 Specific routing of data calls via VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1178.6 CLIP and CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1178.6.1 Routing CLIP and CLIR calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1178.6.2 Routing calls without CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1188.6.2.1 Setting CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1188.6.2.2 Setting CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1198.7 Conversion of call numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1198.8 Overwriting OAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1198.9 Setting number type in OAD/DAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1208.10 Setting the screening indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1228.11 Setting a default OAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1238.12 Setting or removing sending complete byte in setup . . . . . . . . . . . . . . . . . . . . . . .1238.12.1 Exclusion from SIM minutes counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1248.13 Miscellaneous routing methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1248.13.1 Routing calls without a destination number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1248.13.2 Routing calls based on extension prefix or the length of the DAD . . . . . . . . . . . . .1258.14 Changing cause values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1268.15 Call forking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Page 4CELLX 16.29 Additional VoIP parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 1289.1 Signaling parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1299.2 Registrar parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1369.3 Routing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1379.4 Quality parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1389.5 Compression parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1429.6 Fax/modem parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1439.7 DTMF parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14410 System maintenance and software update . . . . . . . . . . . . . 14510.1 Configuration errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14610.2 Status and error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14610.3 Software update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15110.4 SNMP agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15210.5 DNS forwarder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15510.6 ipupdate - DynDNS client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15610.7 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15710.7.1 ISDN trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16010.7.2 GSM/CDMA/UMTS trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16110.7.3 VoIP trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16210.7.3.1 Interface IP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16310.7.3.2 Internal protocol interface (to ISDN, mobile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17110.7.3.3 H.245 messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17310.7.3.4 RAS (registration, admission, status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17710.7.3.5 ENUM output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18110.7.3.6 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18210.7.4 Remote output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18510.7.5 SMTP trace output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18610.7.6 Number portability trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18910.7.7 DTMF tone trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18911 Feature packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19211.1 Activating the license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19311.2 Two stage dialing/callback server functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . .19411.2.1 Announcements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19511.2.2 Two stage dialing with DTMF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19511.2.3 Callback with DTMF and OAD as callback number . . . . . . . . . . . . . . . . . . . . . . . . . .19711.2.4 Callback with DTMF and preconfigured callback number . . . . . . . . . . . . . . . . . . . .19811.2.5 Callback to OAD with predefined destination number . . . . . . . . . . . . . . . . . . . . . .19911.2.6 Callback with PIN and preconfigured callback number . . . . . . . . . . . . . . . . . . . . . .19911.3 Least cost routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20011.3.1 Carrier selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20111.3.1.1 Routing entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20111.3.2 Alternative routing settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20111.3.3 Charge models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20211.3.4 Generating charges with the . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20311.4 Online traffic monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Page 5CELLX 16.211.4.1 Generating and retrieving CDRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20611.4.1.1 Call log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20711.4.1.2 Missed calls list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21111.4.1.3 Sending CDRs via e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21311.5 Ported number screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21311.6 Call recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21511.6.1 Call recording procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21611.6.2 Call recording configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21612 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22012.1 No connection to the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22112.1.1 System does not start correctly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22112.1.2 Web interface is not accessible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22212.1.3 IP address settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22312.1.4 Firewall issues and NAT / PAT settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22312.1.5 ISDN access: dial-in number missing or wrong . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22312.1.6 ISDN port not loaded correctly / not active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22412.2 No calls are possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22512.2.1 Call does not arrive on the gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22512.2.2 Call is rejected or not routed to the right destination address . . . . . . . . . . . . . . . .22812.2.3 Call is rejected elsewhere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23112.3 Software update problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

1 About this manualPage 7CELLX 16.2Congratulations on the purchase of your new CELLX! This manual is set up to guide youthrough the step-by-step installation of your CELLX, so that you can follow it through fromthe front to the back. Quick-installation instructions appear in Chapter 4.7 Startup withQuickstart on page 25. Make sure you familiarize yourself thoroughly with the safety and security precautions de-tailed in Chapter 2 Safety and security precautions before you begin to install your CELLX.TELES is not liable for any damage or injury resulting from a failure to follow these safety andsecurity instructions!1.1 OrganizationThis manual is organized into the following chapters.Chapter 1 About this manual introduces the CELLX Systems Manual and how it is setup.Chapter 2 Safety and security precautions contains information about security issuesrelevant to connection with the IP network.Chapter 3 Overview briefly describes the CELLX and its implementation scenarios.Chapter 4 Installation contains information on how to connect and configure thesystem so that it is ready for operation.Chapter 5 Configuration files describes the CELLX’s individual configuration files andparameters.Chapter 7 Mobile configuration options describes mobile configuration entries.Chapter 8 Signaling and routing features describes configuration settings in theroute.cfg used for adjusting PRI signaling and customizing the configuration forspecific scenarios.Chapter 9 Additional VoIP parameters contains additional configuration entries to fine-tune communication with the VoIP peer.Chapter 10 System maintenance and software update describes system messages thatare saved in the protocol file, as well as trace options.Chapter 12 Troubleshooting contains troubleshooting suggestions.1.2 ConventionsThis document uses the following typographic conventions:Bold – items from the GUI menu. Halfbold – items from the GUI and the menu. Code – file names, variables and constants in configuration files or commands in bodytext."Conventions" on page 7 – cross-references can be accessed in the PDF files by a singlemouse click. Configuration data or extracts are written in single-column tables with a gray background.

1 About this manualPage 8CELLX 16.21.3 Safety symbolsThe following symbols are used to indicate important information and to describe levels ofpossible danger.NoteUseful information with no safety implications.AttentionInformation that must be adhered to as it is necessary to ensure that the system functions cor-rectly and to avoid material damage.WarningDanger. Could cause personal injury or damage to the system.Dangerous voltageCould cause injury by high voltage and/or damage the system.Electrostatic dischargeComponents at risk of discharge must be grounded before being touched.ii!!!!

2 Safety and security precautionsPage 10CELLX 16.2Please be sure and take time to read this section to ensure your personal safety and properoperation of your TELES Infrastructure System. To avoid personal injury or damage to the system, please follow all safety instructions beforeyou begin working on your TELES Infrastructure System.TELES Infrastructure Systems are CE certified and fulfill all relevant security requirements. Themanufacturer assumes no liability for consequential damages or for damages resulting fromunauthorized changes.This chapter applies for all Access Gateways. Information that applies only for individualAccess Gateways specifies the system for which it applies.2.1 Safety measures2.2 FCC / Industry Canada Notice This equipment complies with FCC radiation exposure limits set forth for an uncontrolled en-vironment. This equipment must be installed and operated with a minimum distance betweenthe antennas and persons of:58 cm for iGATE and CELLX GSM or20 cm for CELLX CDMA.The minimum distance between gateway antenna and other antennas must be:262cm for iGATE and CELLX GSM or20 cm for CELLX CDMA.The CELLX has been tested and found to comply with the limits for a Class B digital device,pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable pro-tection against harmful interference in a residential installation. This equipment generates,uses and can radiate radio frequency energy and, if not installed and used in accordance withthe instructions, may cause harmful interference to radio communications. However, thereis no guarantee that interference will not occur in a particular installation. If this equipmentdoes cause harmful interference to radio or television reception, which can be determined byDanger 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. Bear in mind that telephone and WAN lines are also energized and can cause electric shocks.Do not insert foreign objects into openings in the device. Conductible objects can cause short circuits that result in fire, electric shock or damage to the device.Do not open the TELES Infrastructure System except to install an additional TELES.Component. Changes in the device are not permitted.Make sure to install the system near the power source and that the power source is easily ac-cessible. Wire your system using only the cables included in the package contents. Use only proper ISDN and Ethernet cables. Be sure to respect country-specific regulations, standards or guidelines for accident prevention. Failure to follow these guidelines could result in system fail-ure or damage.The following information applies for CELLX gateways only. Changes or modifications not ex-pressly approved by the party responsible for compliance could void the user's authority to op-erate the equipment.!!!!

2 Safety and security precautionsPage 11CELLX 16.2turning the equipment off and on, the user is encouraged to try to correct the interferenceby one or more of the following measures:Reorient or relocate the receiving antenna.Increase the separation between the equipment and receiver.Connect the equipment into an outlet on a circuit different from that to which thereceiver is connected.Consult the dealer or an experienced radio/TV technician for help.2.3 EMC protection2.4 System securityThis section describes all points crucial to the TELES Infrastructure System’s system security.The system’s location must support normal operation of TELES Infrastructure Systems accord-ing to EN ETS 300 386. Be sure to select the location with the following conditions in mind.2.5 Servicing the systemRegular servicing ensures that your TELES.System runs trouble-free. Servicing also includeslooking after the room in which the system is set up. Ensure that the air-conditioning and itsfilter system are regularly checked and that the premises are cleaned on a regular basis.Use shielded cables.Do not remove any housing components. They provide EMC protection.Location: Make sure you install the system horizontally in a clean, dry, dust-free location. If possible, use an air-conditioned site. The site must be free of strong electrical or magnetic fields, which cause disrupted signals and, in extreme cases, system failure.Temperature: The site must maintain a temperature between 32 and 113°F and provide ade-quate ventilation. Be sure to guard against temperature fluctuations. Resulting condensation can cause short circuiting. The humidity level may not exceed 80%. To avoid overheating the system, make sure the site provides adequate ventilation.Power: The site must contain a central emergency switch for the entire power source.The site’s fuses must be calculated to provide adequate system security. The electrical facilities must comply with applicable regulations. The operating voltage and frequency may not exceed or fall below what is stated on the label.Antenna: CELLX 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 ser-vices of a professional antenna installer.!!!!

2 Safety and security precautionsPage 12CELLX 16.22.5.1 Replacing componentsIf your system contains any of the following components, replace them according to the fol-lowing table:2.5.2 Protecting the operating systemChanging configuration data and/or SIM card positions may lead to malfunctions and/or mis-routing, as well as possible consequential damage. Make changes at your own risk. TELES isnot liable for any possible damage resulting from or in relation to such changes. Please thor-oughly check any changes you or a third party have made to your configuration!To make changes in or perform tests on the database, make sure your hard disk or flash diskcontains enough storage space. Downloading the log files and deleting them from the systemon a regular basis will ensure your system’s reliability.Be careful when deleting files that you do not delete any files necessary for system opera-tion.To check storage space and/or delete files, use GATE Manager. For more information seethe document TELES.GATE Manager.All files with the extension *.log can be deleted. To save files before deleting them, use theReceive File option in GATE Manager.The following files, if included, must not be deleted:Table 2.1 Component life span Component Life spanFilter pads 6 monthsPower adapter 5 yearsFan 5 yearsTable 2.2 Mandatory files Mandatory filesMandatory system filesboot.rccrypto.vndcrypto5.vndgbox.tz1gbox5.tz1igate.tz1IMEIs.lstlicense.keynetbsd5fs.vndnetbsd5inetbsd5z

2 Safety and security precautionsPage 13CELLX 16.22.6 CDR filesCall Detail Records are intended for analysis of the system’s activity only. They are not de-signed to be used for billing purposes, as it may occur that the times they record are not exact.2.7 Network securityEvery day hackers develop new ways to break into systems through the Internet. While TELEStakes great care to ensure the security of its systems, any system with access through the In-ternet is only as secure as its user makes it. Therefore, to avoid unwanted security breachesand resulting system malfunctions, you must take the following steps to secure your TELESsystem 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 addindividual secure network segments. Access to the system via Telnet, FTP, GUI, or GATE Manager must be passwordprotected. Do not use obvious passwords (anything from sesame to your mother-in-laws maiden name). Remember: the password that is easiest to remember is also likelyto be easiest to crack.The firewall must be able to check the following information and only allow trusted users toaccess 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 netbsdfs.gznetbsdinetbsdzstarttools.tz0xgate.tz1xgate.vndMandatory configuration filesip.cfgpabx.cfgroute.cfgTable 2.2 Mandatory files (continued)Mandatory files

2 Safety and security precautionsPage 14CELLX 16.2For operation and remote administration of your TELES.System, open only the following portsonly when the indicated services are used:Table 2.3 Default ports used for specific services Service Protocol PortFor all systemsFTP TCP 21 (default, can be set)Telnet (for TELES debug access only)TCP 23 (default, can be set)SMTP TCP 25DNS forward UDP 53HTTP TCP 80 (default, can be set)SNTP UDP 123SNMP UDP 161 (default, can be set)H.225 registration, admission, statusUDP 1719 (default, can be set)H.225 signaling TCP 1720 (default, can be set)Radius UDP 1812 (default, can be set)Radius accounting UDP 1813 (default, can be set)GATE Manager TCP 4445 (default, can be set)SIP signaling UDP / TCP 5060 (default, can be set)RTP UDP 29000-29120 (default, can be set)For NMSFTP TCP 21Telnet TCP 23MySQL database TCP 3306NMS protocol TCP 5000NMS update TCP 5001NMS task TCP 5002NMS task TCP 5003NMS Listen TCP 4444For RoutingManagerRadius authentication UDP 1812Radius accounting UDP 1813

3OverviewPage 16CELLX 16.2Mobile phone charges have become an important cost factor for many companies. The CELLX can help reduce these costs, because calls cost significantly less when they occurbetween cell phones that share the same plan. Depending on whether your system includes 4 GSM Boards, CDMA Boards, each CELLX canprovide direct access to the GSM, CDMA or UMTS mobile network with up to 32 mobilechannels – 4 mobile channels per Mobile Board or up to 8 Mobile Boards per CELLX. TheAntenna Splitter Board combines the antennas so that only one or two antennas leave thesystem. The CELLX has 2 PRI ports and VoIP functionality for up to 32 channelsCELLXs can be set upin various national or international locations.3.1 What’s new in version 16.2Enhanced TLS stability in bad IP network conditions.Initial charge now sent immediately after connect by using the InitialCharge=ONoption.New payload G726/40 introduced.DSS1: Improved handling of call forwarding / partial rerouting. Facility messages with 2facility info elements are forwarded transparently from ISDN to ISDN; facility infoelement in Setup message is forwarded transparently from ISDN to ISDN.For calls from or to ISDN or VoIP, a second OAD can now be transmitted.Improved number manipulation with VoipOad and VoipDad commands.New system file tools.tz0 now exists in addition to netbsdfs.gz.System files ipv4.vnd, xgate.vnd, and netbsdi discontinued starting version 16.2.3.2 New Access Gateway product names starting version 16.1Starting from release 16.1., TELES is dividing it’s access gateway product portfolio intoVoIPBox VoIP-ISDN gateways, compact ECOTEL mobile radio gateways and flexibly config-urable iGATE mobile radio gateway systems in a 19” chassis. The product names now clearlyreflect the three different product lines. The following table lists the old and new access gate-way product names.Table 3.1 New Access Gateway product namesOld AGW Product Names New AGW Product Names since version 16.1.VoIPBOX BRI VoIPBox BRIVoIPBOX PRI VoIPBox PRIVoIPBOX GSM ECOTEL GSMVoIPBOX UMTS ECOTEL 3GiGATE GSM iGATE GSMiGATE 3G iGATE 3G

3OverviewPage 17CELLX 16.23.3 How CELLX worksThe CELLX is connected to the PBX and to the mobile network.During outgoing calls from the PBX or IP network to mobile, dialed digits are comparedwith the routing-table entries for various mobile networks. The calls are then routedthrough the corresponding SIMs in the CELLX and forwarded to the number dialed.Only the connection from the SIM in the CELLX to the mobile number in the samemobile network is charged.Inbound c alls are forwarded to your PBXThe CELLX contains SIM cards with your company’s billing plan3.4 Supported implementation scenariosIn each of the following scenarios, calls are routed through individual gateways into the mo-bile network:a) Failover applicationIn case of a landline connectivity failure, the PBX routes outgoing calls to the CELLXwhich in turn forwards the calls directly to the mobile network.Figure 3.1 Failover application

3OverviewPage 18CELLX 16.2b) one-x mobile UC integrationA company’s cell-phone users have smart phones running Avaya’s one-X Mobile client.The one-X mobile client requests a callback from the PBX via IP whenever these usersmake a call. This callback is then routed through the CELLX. As soon as the callback isanswered, the PBX calls the B party and connects the call.Figure 3.2 one-x mobile UC integration

4 InstallationPage 20CELLX 16.2Follow the easy instructions to set up your CELLX in a matter of minutes. Implementation ofindividual scenarios requires adjustments to the appropriate interfaces. Tips for basic settingsare described here. Links to relevant chapters are provided for more specific configurationchanges.4.1 ChecklistThe following checklist provides step-by-step installation instructions.1. Check the package contents2. Install the device3. Connect the Ethernet4. Connect the T1/E1 trunks (optional)5. Connect the antennas6. Using Quickstart, set the configuration (IP address)7. Check functionality (using the LEDs)8. Secure the LAN connection9. Secure connection with the configuration program4.2 Package contentsYour CELLX package contains the following components. Check the contents to make sureeverything is complete and undamaged. Immediately report any visible transport damages tocustomer service. If damage exists, do not attempt operation without customer-service ap-proval:1 CELLX1 power supply cable1 crossover PRI cable1 RJ-45 LAN cable with gray connectors; 3 meters1 copy of quick installation instructions1 CD containing Quickstart, GATE Manager, system manual and default configurationfilesMobile antennas (optional)4.3 Hardware descriptionThroughout this manual, the following boards will be referred to as Mobile Board, unless oth-erwise specified:4 GSM BoardCDMA BoardThe CELLX is available in expansion levels from 4 to 32 mobile channels. The following pagesdescribe installation of the CELLX .Figure 4.1 shows the rear view of a CELLX, which contains the following boards:

4 InstallationPage 21CELLX 16.2From left to right:Base BoardMobile Board (for mobile channels 1-4)Mobile Board (for mobile channels 5-8)Mobile Board (for mobile channels 9-12)Mobile Board (for mobile channels 13-16)Optional Antenna Splitter BoardMobile Board (for mobile channels 17-20)Optional Mobile Board (for mobile channels 21-24)Optional Mobile Board (for mobile channels 25-28)Optional Mobile Board (for mobile channels 29-32)Figure 4.1 4HU CELLX4.4 Installation requirementsBefore installing your CELLX, make sure you have the following connections in place:Ethernet connectionAntenna connection(s)Optional ISDN PRI connection to PBXPowerInsert the SIM cards into the SIM card carrier, the SIM card carrier into the Mobile Board.4.4.1 Ethernet wiringTo connect the CELLX’s Ethernet port to your local network, connect the system to an Ether-net switch in your network. Use the three meter cable with gray connectors.

4 InstallationPage 22CELLX 16.24.4.2 PRI wiring4.4.2.1 TELES to TBR12If you are connecting an CELLX to T1/E1 and need to change the assignment of an adapter,assign the pins as follows. Connectors on cables included with the CELLX will be gray forTELES TE and gray for NT on the remote device, blue for TELES NT, and green for TE on theremote device:Figure 4.2 TELES to TBR124.4.3 Antenna connectionPlug an antenna cable into each of the SMA jacks. If the system contains a AntennaSplitter Board, plug the antenna(s) in there. If not, plug them into the jacks on theMobile Board.4.4.4 SIM card assignmentIf your gateway is connected to a vGATE, the following information does not apply.Each gateway has one or more slots for SIM card carriers. The SIM card carrier contains theSIM cards for the individual mobile channels. Insert the SIM cards in the SIM card carrier andthen insert the SIM card carrier into the gateway.SIM card carriers are available in two versions, SIM24 and SIM4, whereby the number showsthe number of available SIM card positions.Antennas connected to the CELLX must be installed by a qulaified technician according to all necessary safety requirements and the antenna’s installation specifications. The antenna adaptor does not provide power surge protection.iiYou 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.ii

4 InstallationPage 23CELLX 16.2SIM cards are mounted on the front and back of the SIM24 module (Figure 4.3) or the frontof the SIM4 module (Figure 4.4). As a guide to help you distinguish top from bottom on theSIM24 module, SIM0-5 and SIM12-17 are printed in the upper corner near the module’s han-dle, as can be seen in Figure 4.3. The SIMs on the SIM4 module are numbered from right toleft, with one SIM assigned to each mobile channel in ascending order.Figure 4.3 SIM24 module: front and rear viewFigure 4.4 SIM4 moduleIf a SIM24 carrier is used, one out of six SIM cards can be assigned to a mobile controller. Toconfigure that, an index has to be set in the pabx.cfg Subscriber line.The following examples show how a SIM card at a certain position on the SIM24 carrier isassigned to a defined mobile controller and what index it needs for assignment.Table 4.1 shows the assignment to the mobile controllers 00 to 03. The 24 available SIM cardpositions on the SIM24 carrier are listed in the body rows. The 6 different SIM cards whichare available for each mobile controller are indexed in the heading row. This index needs tobe entered in the pabx.cfg Subscriber line behind the SMSC entry. Example 4.1 shows thatthe SIM card at position 0 on the SIM24 carrier is assigned to mobile controller 00 by giving

4 InstallationPage 24CELLX 16.2it the index 1. The SIM card which is at position 1 on the SIM24 carrier is assigned to the mo-bile controller 01 by also giving it the index 1. SIM card number 10 on the SIM24 carrier isassigned to mobile controller 02 with the index 3. Analogously, SIM card number 11 is as-signed to mobile controller 03 with the index 3.The following corresponding example shows how SIM cards at position 4, 5, 6, and 7 on theSIM24 carrier are assigned to the mobile controller 08 to 11. They all get the index 2 in theSubscriber line.Table 4.1 SIM card assignment to mobile controllers 1 (SIM24 carrier)Index in Subscriber line 1 2 3 4 5 6Controller/Subscriber00 0 4 8 12 16 20Controller/Subscriber01 15 9 13 17 21Controller/Subscriber02 2610 14 18 22Controller/Subscriber03 3 7 11 15 19 23Example 4.1 SIM card assignment to mobile controllers 1 (SIM24 carrier)Subscriber00=TRANSPARENT GSM[0000,00000,+491770610000,1,1,1,SIM24] ALARMSubscriber01=TRANSPARENT GSM[0000,00000,+491770610000,1,1,1,SIM24] ALARMSubscriber02=TRANSPARENT GSM[0000,26202,+491770610000,3,1,1,SIM24] ALARM Subscriber03=TRANSPARENT GSM[0000,00000,+491770610000,3,1,1,SIM24] ALARMTable 4.2 SIM card assignment to mobile controllers 2 (SIM24 carrier)Index in Subscriber line 1 2 3 4 5 6Controller/Subscriber08 0 48121620Controller/Subscriber09 15913 17 21Controller/Subscriber10 2 610 14 18 22Controller/Subscriber11 3711 15 19 23Example 4.2 SIM card assignment to mobile controllers 2 (SIM24 carrier)Subscriber08=TRANSPARENT GSM[0000,00000,+491770610000,2,1,1,SIM24] ALARMSubscriber09=TRANSPARENT GSM[0000,00000,+491770610000,2,1,1,SIM24] ALARMSubscriber10=TRANSPARENT GSM[0000,26202,+491770610000,2,1,1,SIM24] ALARM Subscriber11=TRANSPARENT GSM[0000,00000,+491770610000,2,1,1,SIM24] ALARM

4 InstallationPage 25CELLX 16.2In a SIM4 carrier, each SIM card corresponds with one mobile controller. In the pabx.cfgSubscriber line each SIM card always gets the index 1, as shown in the example below.4.5 Preparing for installationEach computer that is to communicate with the CELLX requires a network connection. DHCPcan be used to automatically assign an IP address and the netmask. If you don’t use DHCP,please have the following information for connection to your network available:IP address in the local network for the CELLX to be configuredNetmask for the CELLX to be configuredDefault gateway for CELLX to be configured4.6 Hardware connectionConnect your computer with the local networkConnect the CELLX with the local networkIf you choose to connect the CELLX to ISDN, use the ISDN connection cables includedin the package contents to connect the CELLX with your PBX and/or the PSTN accordingto the required port configuration.Connect the CELLX to the power supply.4.7 Startup with QuickstartQuickstart is an application that helps you to configure the IP settings of your CELLX quicklyand conveniently without changing any network settings on your computer. Quickstart can be installed on any of the following operating systems:Windows 2000Windows XPWindows VistaWindows 7If you are using any of these operating systems, please follow the instructions in this chapter.4.7.1 Installing QuickstartMake sure the GATE Manager is not running on your computer. To install Quickstart on yourcomputer, insert the CD and select Quickstart from the menu. Example 4.3 SIM card assignment to mobile controllers (SIM4 carrier)Subscriber00=TRANSPARENT GSM[0000,00000,+491770610000,1,1,1,SIM4] ALARMSubscriber01=TRANSPARENT GSM[0000,00000,+491770610000,1,1,1,SIM4] ALARMSubscriber02=TRANSPARENT GSM[0000,26202,+491770610000,1,1,1,SIM4] ALARM Subscriber03=TRANSPARENT GSM[0000,00000,+491770610000,1,1,1,SIM4] ALARMBear in mind that the preconfigured CELLX’s default IP address is 192.168.1.2. If it is already being used in your local network, you must run Quickstart without a connection to your local network. This can occur using a back-to-back Ethernet connection from your computer to the CELLX. If the desired IP address for the CELLX is not in your network, you must assign your computer a temporary IP address from this range.ii

4 InstallationPage 26CELLX 16.2When asked if you want to install components on your machine, click Install.Click Next in the introduction window to begin installation of the Quickstart. Once installation begins, click Next to install Quickstart in the predefined folder. To install itin another location, click Browse and select a folder from the browser that appears. Thenclick Next.Click Close to exit when installation is complete.4.7.2 Configuration with QuickstartNow you can use Quickstart, to set up your CELLX’s IP configuration. Open Quickstart.exe.The program will automatically search for your CELLX in the local network. For Quickstart, thesource UDP port is 57445. It might be necessary to change the firewall rules on your system. Click Search if you would like to restart the search. When the program has found your CELLX,it will appear in the window. As soon as it appears, you can end the search by clicking Stop.Figure 4.5 QuickstartThe system’s icon will appear in gray if it is unconfigured. Once it has been configured, it willappear in green. The serial number appears as the system’s name. The CELLX is partially pre-configured. The configuration files pabx.cfg and route.cfg are already on the system. Onlythe system’s IP-related entries must be set. Individual port adjustments are to be made man-ually later. Port properties can be changed and parameters can be assigned then.To change the appearance of the window, click Large Icons, Small Icons or Details in theView menu. In the following description, we will use the Details View, which contains thefollowing columns:Table 4.3 Quickstart details view columns Heading DefinitionIdentifier This column lists the CELLX’s serial number.IP Address This column lists the CELLX’s IP address.Configured An X means the CELLX contains the configuration files.# of VoIP Ctrls This column lists the number of VoIP Modules installed in the CELLX. Each VoIP Module represents one VoIP controller.VoIP Channels This column shows the number of VoIP channels per VoIP Module.Type Lists the type of the system.

4 InstallationPage 27CELLX 16.2In the Options menu, you can suppress or activate ICMP ping to test the Internet connection.To perform the initial configuration of the system, double-click the icon or right-click and se-lect Configure. The IP Settings dialog will appear. If you want the gateway to use a dynamicIP address, activate the checkbox DHCP. This will deactivate the next three lines. Your DHCPserver will automatically provide all of the other necessary information. If you do not have aDHCP server, leave the DHCP checkbox empty. The default IP address appears in the IP Ad-dress box. Enter a new IP address. If the address you enter already exists in the network, youwill be notified to choose another address at the end of the configuration process. Enter thesystem’s netmask in the Mask dialog box. Enter the IP address for the Default Gateway.Click Finish. Figure 4.6 Quickstart configuration: IP settingsNow the IP settings are configured; all other processes run automatically. First the system’s IPaddress will be changed and then the system will start with the new IP address. If you right-click the system’s icon in the main window and choose Temporarily ConfigureIP Address, only the IP address for the system’s first Ethernet interface and the netmask willbe temporary changed. This can be helpful if you want to set up local remote access to theBox An X means the system is a VoIPBox BRI.CF Mounted An X means the CELLX contains a compact flash disk.Table 4.3 Quickstart details view columns (continued)Heading DefinitionThere is no internal time generation for the system when the power is interrupted. That means the default time is used when the system is restarted or rebooted! Therefore it is important to set the system time with an NTP server.If the system is connected via ISDN, a clock may come from the network connected to the cor-responding port. Enter TIME in the pabx.cfg’s Subscriber line for the TE port to retrieve the time from the port.ii

4 InstallationPage 28CELLX 16.2system and use other IP settings on the remote device than the system’s IP configuration inthe network. Bear in mind that the functions on the system’s first Ethernet interface workwith the new settings.Now you can complete the system’s configuration using the GUI (please see Chapter 4.8 Star-tup via GUI on page 28).4.8 Startup via GUISystem configuration can occur via the GUI. Figure 4.7 GUIWe recommend you use Internet Explorer 6/7/8. Simply open a browser, enter the system’sIP address in the address bar, and click Login in the navigation menu on the left. Enter theusername teles-carrier and the password tcs-carrier to access the system. Figure 4.8 GUI faststartUsing the navigation menu on the left, click Faststart to configure the system. Follow thesteps as they appear.

4 InstallationPage 29CELLX 16.2To edit the default configuration, follow the directions in Chapter 5 Configuration files. Up-load the configuration files into the /boot directory.4.9 LED functionality4.9.1 Ethernet port LEDsEach ethernet port has 2 LEDs to show its status. The left LED blinks to indicate data traffic.The right LED is currently not used.4.9.2 Base Board PRI port LEDsEach PRI port has one red and one green LED to show the port’s status.The red LED displays the status of the bypass relay that connects the ports with each otherwhen the relay between the PRI ports is off. That means when the system is connected be-tween a PBX and the PSTN, it is transparent when the LED is red.The green LED displays whether or not layer 1 is active on the PRI port’s connected cable. 4.9.3 Mobile Board SIM card LEDsOn the spine of the Mobile Board, to the right of the SIM card module, two columns of greenLEDs display the status of each mobile channel. Figure 4.9 Mobile Board SIM card LEDsTable 4.4 Base Board PRI Port LEDsLED DescriptionRed ON The system and bypass relay are inactive (normal-ly during the startup phase).Red OFF The system has started and the bypass relay is ac-tive.Green ON Layer 1 is active.Green OFF Layer 1 is inactive.

4 InstallationPage 30CELLX 16.2The LEDs in the upper column show the general operational status of the SIM cards, whilethe status of the mobile channels is displayed in the lower column.Table 4.5 contains a description of the LEDs and what they mean:Table 4.5 Mobile Board LEDsOperational Status Connection Status DefinitionOFF OFF The mobile channel is not oper-ational because:No external power supplySIM module slot is emptyNo SIM cardOFF Blinking slowly Not possibleOFF Blinking quickly Not possibleOFF ON Not possibleBlinking slowly OFF The SIM card is attached, but the mobile channel is not oper-ational because:Mobile channel is in logon phaseMobile channel’s status is unknownBlinking slowly Blinking slowly Not possibleBlinking slowly ON Not possibleBlinking quickly OFF The mobile channel is not oper-ational because:SIM card has been blockedReception field strength below limitBlinking quickly Blinking slowly Not possibleBlinking quickly Blinking quickly Status during initializing phase (system start up). Display changes when status of mobile changes.Blinking quickly ON Not possibleON OFF The mobile channel is opera-tional, the SIM card has logged on.ON Blinking slowly Not possibleON Blinking quickly The mobile channel is opera-tional, the SIM card has logged on, a connection is being set up on this channelON ON The mobile channel is opera-tional, the SIM card has logged on, a connection has been set up on this channel

4 InstallationPage 31CELLX 16.24.10 Remote access and access securityAfter the system has been configured and all cables are connected, remote administrationand maintenance can occur with the GATE Manager (Chapter 4.10.1), the GUI(Chapter 4.10.2)or via FTP (Chapter 4.10.3).4.10.1 GATE Manager Figure 4.10 GATE ManagerThe GATE Manager administration and maintenance software offers a broad range of func-tions. The GATE Manager is user friendly and can be customized to suit your needs. The following maintenance functions are possible:Display system information and network element status.Retrieve and display configuration files.Restart network elements.Use of a trace option for checking functions and fault diagnosis. Option to use anexternal tool, for example to display and break down trace data.Update the system software and configuration tables.Retrieve CDRs (Call Detail Records).Display the current connections (status).Display statistical information for network elements and interfaces.Display the status of the interfaces.Use the CD enclosed in your package contents to install the GATE Manager. For a detaileddescription of installation and implementation of the GATE Manager, please refer to theGATE Manager and Utilities Programs Manual.GATE Manager remote access can occur via IP or ISDN. GATE Manager access via IP uses port4444 as source TCP port and port 4445 as destination port. You can change the port in thepabx.cfg file using the following parameter: MoipPort=4567.Bear in mind that the same port must be configured in the GATE Manager. The TCP port canbe specified behind the IP address and a colon: IP:172.20.25.5:4567.In the default configuration, ISDN remote access is disabled. To configure the system so thatcertain data calls are received as remote administration calls, make the following changes inthe pabx.cfg: RemoteCode=BBBAdd the following mapping to the route.cfg:MapAll<direct>=BBB DATAMake the following entries in the route.cfg if the system is to handle all ISDN data calls asremote-administration calls:

4 InstallationPage 32CELLX 16.2MapAll?=BBB DATA 4.10.2 Graphical user interface (GUI)Remote access can occur via the GUI. Even users with little experience can easily configurestandard system settings with this interface. Simply open a browser and enter the system’s IPaddress in the address bar. Figure 4.11 GUIThe following administrative levels apply:Carrier mode (full access)User: teles-carrierPassword: tcs-carrierAll configuration pages can be accessed in this mode.Example 4.4 Carrier mode (full access)[httpd]PwdUser=k24X0sdc.uMcMPwdAdmin=k2UMj19qtovzIPwdCarrier=k2jryo6Xd5vN6Never copy these entries from one system to another, as the encryption is unique for each sys-tem.ii

4 InstallationPage 33CELLX 16.2Administrator ModeUser: teles-adminPassword: tcs-adminThis access level is for the user network’s administrator. All IP and routing entries, with theexception of VoIP carrier entries, can be set here.Read-Only ModeUser: teles-userPassword: tcs-userNo configuration changes can be made at this level. Only status and statistics can be retrieved.Of course, these configuration levels correspond with the most important scenarios. The pass-words are saved in the ip.cfg in encrypted form:PwdCarrier=<crypt>PwdAdmin=<crypt>PwdUser=<crypt>The user interface is divided into the following main sections: All of the user interface’s pages contain Help buttons and links to the online help, which pro-vides a detailed description of all of the individual configuration settings.4.10.3 FTPRemote access can also occur via FTP. You can use FTP to transfer configuration files. You canalso carry out functions and traces with raw commands. Use the username teles and thedefined password to connect to the system with FTP.Table 4.6 GUI: sections Section DescriptionUser Data Here you can change the user passwords and the language for the GUI.Faststart Faststart helps you to configure the system settings of your quickly and conveniently.System Settings IP Settings: Settings for the Ethernet interfaces and related services.Port Settings: Settings for the ECOTEL GSM ports.VoIP Settings: VoIP settings for the SIP or H.323 carrier.Telephony Routing:Routings for telephone numbers.System Overview Overview of system information and drivers.Commands Here you can activate a configuration or restart the system.

4 InstallationPage 34CELLX 16.2The following entries in the pabx.cfg ensure the security of your FTP access: Once you have access to the system, you will be in the folder /home/teles. To upload ordownload configuration files change to the directory /boot. To download log files, changeto the directory /data if the system contains a flash disk. Otherwise change to the directory/boot.The following commands can be carried out via FTP access: If your FTP client does not support the site command, try “literal site” instead.4.10.4 Setting a password for remote accessThe following entry ensures the security of your remote access. Use the mkpwd.exe tool togenerate the password. You will find it on the enclosed CD in the directory pwd. Start the program in a command window with the entry mkpwd <password>. The outputshows the encrypted password. Enter the encrypted password in the configuration filepabx.cfg’s parameter line as follows.Table 4.7 FTP security entries FTP SecurityFtpdPort=<port>Defines the FTP access port (default 21).RemotePassword=<password>Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.10.4 for in-structions on how to enter an encrypted password in the pabx.cfg. If you do not define a pass-word, access to the system via GATE Manager occurs without a password, and FTP access occurs with the default password tcs-ag.Table 4.8 FTP commands Command Functionsite xgboot Boots the entire system.site xgact Activates the configuration.site xgact 1-19 Activates the Night section corresponding with the number 1-19.site xgtrace 0 Deactivates trace.site xgtrace 1 Activates layer 2 trace.site xgtrace 2 Activates layer 3 trace.Example 4.5 Password for remote accessRemotePassword=<crypt>

4 InstallationPage 35CELLX 16.2When the file has been transferred to the system and the configuration has been activated,access to the system can occur only with the password. Don’t forget to memorize the pass-word!If you do not define a password, access to the system via GATE Manager occurs without apassword, and FTP access occurs with the default password tcs-ag.

5 Configuration filesPage 37CELLX 16.2This chapter describes the basic setup and the most commonly used entries for the configu-ration files. Configuration of CELLXs is managed in the following three files: The default configuration with the IP address 192.168.1.2 is active when the files are not onthe system. You can configure the files using GATE Manager or via FTP (user teles, passwordtcs-ag). If you use the GUI to make configuration changes, the files will be adjusted automat-ically.Make sure you secure the system with new passwords following configuration and rememberto memorize the passwords! These configuration files contain all system-specific settings and are used when the systemstarts. Comments included in these files must begin with a semicolon. They do not need tobe at the beginning of a line. Configuration files must end with an empty line.Please save a backup of the files pabx.cfg and route.cfg before starting configuration.The configuration files follow these conventions: Individual files are divided into sections.These sections always begin with a line entry in square brackets. The basic required sectionsare in these files: Table 5.1 Configuration filesFile Functionip.cfg This file is for the basic configuration of the Ethernet interfaces.pabx.cfg This file is for system-specific and port-specific settings.route.cfg This file is for call-routing entries.Changing configuration data and/or SIM card positions may lead to malfunctions and/or mis-routing, as well as possible consequential damage. All changes are made at own risk. TELES is not liable for any possible damage out of or in relation with such changes. Please do there-fore thoroughly check any changes you or a third party have made to your configuration.iiiiTable 5.2 Required configuration file sectionsSection File Function[System] pabx.cfgroute.cfgip.cfgThis section contains the sys-tem’s basic settings. [Night<num>]EXAMPLE: [Night1][Night2]pabx.cfgroute.cfgThis section contains time de-pendent entries that only apply for limited times.[emac0] ip.cfg This section contains the IP configuration for the first Ethernet interface.

5 Configuration filesPage 38CELLX 16.25.1 Configuration file ip.cfgThe basic settings for the two Ethernet interfaces are entered here. One interface usually suf-fices. The second interface can be used for special requirements, for example as a hub port,DSL router or vLAN interface. Generally, these settings are entered once and then left un-changed. This file contains the following sections, which must appear in the order given: 5.1.1 System section configurationThe [System] section contains entries that define the default gateway and/or special routingentries. To define the standard gateway, use the following entry to set the IP address:DefaultGw=<ip addr>Table 5.3 Sections in the ip.cfg fileSection Function[System] (required) This section contains entries that define the default gateway and/or special routing entries.[emac0] (required)[emac1] (optional)The Ethernet Media Access Controller section(s) define the physical Ethernet interface(s).[nat] (optional) This section includes settings for Network Address Translation.[bridge0] (optional) These section(s) contain settings for the second Ethernet con-troller in bridge mode.[pppoe<x>] (optional) These sections contain settings for direct connection between the system and the DSLAM when the PPPoE protocol is used. <x> can be 0 or 1.[firewall] (optional) This section contains settings for activating the system’s fire-wall.[altqd] (optional) This section enables prioritization of VoIP packets in the CELLX through an IP network using bandwidth control.[dhcpd] (optional) This sections contains a list of parameters and settings for the DHCP server in the system. It is divided into global settings for the server and parameters for the DHCP subnet.[xppp<x>] (optional) This section contains settings for point-to-point dial-up setup via ISDN.[vlan<x>] (optional) These section(s) contain settings for the virtual networks. <x> can be anything from 0 to 9.Example 5.1 System section configuration 1[System]DefaultGw=192.168.1.254

5 Configuration filesPage 39CELLX 16.2If you must route specific net ranges to gateways other than what is defined in the defaultroute, make the following entries in the [System] section:Route=<target range> -netmask <ip mask> <ip gateway>If only certain routes apply, leave the line DefaultGw empty.5.1.2 Ethernet interface configurationThe system includes two Ethernet interfaces (emac0 and emac1). Only the first is active in thedefault configuration. Therefore, make sure you plug the cable into the right controller. Thesecond Ethernet interface can be configured as needed.The following settings are possible for the sections [emac0] (matched to the first Ethernetcontroller) and [emac1] (matched to the second Ethernet controller):IpAddress=<ip addr>/<netmask> The IP address is entered in decimal notation, followed by a slash (/) and the netmask in bitnotation.The following entry is used to allocate an IP address via DHCP: IpAddress=dhcpThe following entry is used in the [emac1] section if operation of the system occurs in bridgemode.IpAddress=up5.1.3 GUI settingsThe following parameter is used to change the GUI port in the section [httpd] (default 80):GuiPort=<num>Bear in mind that the passwords for different access levels are not set here. The encryptedpasswords are stored here and can only be changed via GUI (see Chapter 4.10.2 on page 32).Example 5.2 System section configuration 2[System]DefaultGw=192.168.1.254Route=10.0.0.0 -netmask 255.0.0.0 192.168.1.1Example 5.3 Ethernet interface configurationIpAddress=192.168.1.2/24Example 5.4 GUI settings[httpd]GuiPort=80PwdUser=k24X0sdc.uMcMPwdAdmin=k2UMj19qtovzIPwdCarrier=k2jryo6Xd5vN6

5 Configuration filesPage 40CELLX 16.25.1.4 Bridge configurationA bridge can connect two networks with each other. A bridge works like a hub, forwardingtraffic from one interface to another. Multicast and broadcast packets are always forwardedto all interfaces that are part of the bridge. This can occur on the Ethernet or VLAN level:BrConfig=add <interface-x> add <interface-y> upActivating another Ethernet interface in this way is useful, for example, when the Ethernetswitch does not have any more ports available for connection of the system. You can simplyunplug a cable and plug it into the system’s second Ethernet interface.5.1.5 NAT configurationThe NAT (Network Address Translation) module translates IP addresses from the local net-work to an IP address or range on a public interface. All rules are defined in the [nat] section: Example 5.5 Bridge configuration[bridge0]BrConfig=add emac0 add emac1 upTable 5.4 NAT configuration map=<interface> <local network address/mask> -> <public network address/mask> <op-tional entries>This parameter maps the IP address in the local network to the IP address in the public network.<interface> Defines the translated interface or protocol:emac1 The system’s second Ethernet interfacepppoe0 Protocol used for DSL connectionsxppp<0> Protocol used for ISDN and CDMA dial-up connections<local network address/mask> The IP address is entered in decimal notation, followed by a slash (/) and the netmask in bit notation. The entire local net-work range is configured.<public network address/mask> Defines the public network range, with network address and mask (usually exactly one address), into which the local IP ad-dresses are to be translated. The IP address is entered in dec-imal notation, followed by a slash (/) and the netmask in bit notation.<optional entries> Special rules can be defined for some services or protocols. The system can serve as a proxy for FTP: proxy port ftp ftp/tcpSpecial ports for the public address(es) can be assigned for the protocols TCP and UDP. The range is defined by the start and end ports:portmap tcp/udp <start port>:<end port>If no optional entry is defined, all other addresses will be translated without special rules.rdr=<interface> <public network address/mask> port <port> -> <local network address/mask> port <port_number> <protocol>This parameter sends packets from one port and IP address to another.

5 Configuration filesPage 41CELLX 16.2The following NAT settings are for a system in which PPPoE (DSL) is used toward the Internet.The local network range 192.168.1.0 Class C is translated with the following rules:The proxy mode is used for FTP. All other TCP and UDP packets are mapped to the external ports 40000 to 60000. There are no special rules for any other services.Incoming requests to port 80 and 443 in the public IP address 192.168.1.100 areredirected to ports 80 and 443 in the local IP address 192.168.1.100.5.1.6 PPPoE configurationThe protocol Point-to-Point over Ethernet is used for DSL communication with the DSLAM.That means the system can connect directly with a DSL modem. All necessary information for setup of the PPPoE connection is defined in the [pppoe<x>] sec-tion. That means username, password and authentication protocol are set here. The Ethernetinterface is emac1 and the gateway can also be defined. The parameter PppoeIf defines thephysical Ethernet interface used (always emac1). The settings are entered as follows: Bear inmind that configuration of the firewall, the NAT module and prioritization of the VoIP packetsmust be considered when routing voice and data through the DSL line.<interface> Defines the translated interface or protocol:emac1 The system’s second Ethernet interfacepppoe0 Protocol used for DSL connectionsProtocol used for ISDN and CDMA dial-up connections<public network address/mask> Defines the public network range, with network address and mask (usually exactly one address), into which the local IP ad-dresses are to be translated. The IP address is entered in dec-imal notation, followed by a slash (/) and the netmask in bit notation.<port> Defines the port number.<local network address/mask> The IP address is entered in decimal notation, followed by a slash (/) and the netmask in bit notation. The entire local net-work range is configured.<protocol> Defines the protocol. tcp and udp are possible.watch=<interface 1> <interface 2> ... <interface n>Enter all interfaces that you have configured. If an interface is activated, the NAT table is resetted to ensure correct IP address translation.Table 5.4 NAT configuration (continued)Example 5.6 NAT configuration[nat]map=emac1 192.168.1.0/24 -> 0/32 proxy port ftp ftp/tcpmap=emac1 192.168.1.0/24 -> 0/32 portmap tcp/udp 40000:60000map=emac1 192.168.1.0/24 -> 0/32rdr=emac1 0/0 port 80 -> 192.168.1.100 port 80 tcprdr=emac1 0/0 port 443 -> 192.168.1.100 port 443 tcp

5 Configuration filesPage 42CELLX 16.2The following entry will create the interface pppoe0, with the username user and the pass-word pwd. The PAP authentication protocol is used. The default route occurs via DSL.5.1.7 Firewall settingsIn the following example, only port 4445 allows incoming connections from the IP address192.168.1.10. All others will be blocked.Example 5.7 PPPoE configuration[pppoe0]PppoeIf=emac1 User=userPwd=pwdAuthProto=papRoute=0.0.0.0The firewall settings provide options for limiting or denying access to and from the system. If you do not configure this section, the firewall is inactive and access is unlimited. Make sure you configure the firewall rules carefully. The rules are processed from top to bottom. If you use the option quick, you will break the sequence. We recomend that you put the most re-strictive rule at the end of the configuration.iiExample 5.8 Firewall settings 1[firewall]fw=pass in quick on emac0 proto tcp from 192.168.1.10/32 to any porteq 4445 flags S keepstate keep frags fw=block in log quick on emac0 allTable 5.5 Settings in the [firewall] section of the ip.cfg [firewall]fw=<mode> <direction> <list><mode> Two modes are possible for permitting or deny-ing access:pass permit accessblock deny access<direction> Possible directions are in and out:in external to internalout internal to external<list> All other entries specify the other settings for the corresponding firewall rules and are optional. The order in the line is as listed below:log Records non-matching packets.

5 Configuration filesPage 43CELLX 16.2quickAllows short-cut rules in order to speed up the filter or override later rules. If a packet matches a filter rule that is marked as quick, this rule will be the last rule checked, allowing a short-circuit path to avoid processing later rules for this packet. If this option is missing, the rule is taken to be a "fall-through rule, meaning that the result of the match (block/pass) is saved and that pro-cessing will continue to see if there are any more matches.on <interface>The firewall rule is used only for the defined interface (for example emac0, pppoe0).from <networkaddress/mask>to <networkaddress/mask>from defines the source IP-address range for incoming packets. to defines the target IP-address range for outgoing packets. The IP address appears in decimal notation, followed by a slash (/) and the netmask in bit notation. any stands for all IP addresses (example: to any).NOTE: If you use the rule pass in/out in combination with the option from <ip> to <ip>, you must specify a protocol number with proto and a port number. If you not specify the port, the system may not be reachable. EXAMPLE:fw=pass in quick on pppoe0 proto tcp from any to any port eq 4445proto <protocol>defines the protocol, for which the rule is valid (example: proto tcp, proto udp, proto icmp).port eq <num><num> defines the port as number (example: port eq 4445).keep stateEnsures that the firewall checks packets from the beginning to the end of a session. This is nec-essary, as the firewall cannot process when a session begins or ends.flags SOnly syn. packets are accepted and recorded in the state table. In conjunction with keep state, packets from sessions that have been inactive will also be routed. The advantage of this entry is that random packets will not be accepted.keep fragsFragmented packets are also routed.Table 5.5 Settings in the [firewall] section of the ip.cfg (continued)[firewall]fw=<mode> <direction> <list>

5 Configuration filesPage 44CELLX 16.25.1.8 Bandwidth controlIn many implementation scenarios, the CELLX in router mode (for example as DSL router)sends voice and data traffic through a connection with limited bandwidth. This can lead tolost voice packets that arrive too late to be used in the voice stream. To avoid lost packets,this QOS setting prioritizes packet transmission. You must set the priority for voice signalingand for the voice packets. That means you must prioritize SIP/H.323, RTP and RTCP. You willfind the ports used in Table 5.14, in the following entries:H225PortSipPortVoipRtp PortVoipRtpPortSpacingDifferent ports are used for RTP and RTCP, depending on the configuration.The parameter VoipRtpPort shows the first RTP port used. The corresponding RTCP port is thenext one up. The parameter VoipRtpPortSpacing shows the next RTP port (RTP port + portspacing).Example 5.9 Firewall settings 2[firewall]; loopbackfw=pass in quick on emac0 allfw=pass out quick on emac0 all; traffic to outgoingfw=pass out quick on pppoe0 proto tcp all flags S keep state keep fragsfw=pass out quick on pppoe0 proto udp all keep state keep fragsfw=pass out quick on pppoe0 proto icmp all keep state keep frags; incoming trafficfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 21 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 23 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state ; icmp trafficfw=pass in quick on pppoe0 proto icmp all keep state; other will be blockedfw=block in log quick on pppoe0 allfw=block out log quick on pppoe0 allTable 5.6 Settings in the [altqd] section of the ip.cfg Interface=<interface> bandwidth <bw> priqDefines the interface for which the rule applies.<interface> Sets the interface for which prioritization applies (e.e. pppoe0).<bw> Sets the bandwidth that is available on the inter-face in Kbit/s (for example 256K).priq Priority qeueing. A higher priority class is always served first.classPrio=<interface> <class> root priority <prio>

5 Configuration filesPage 45CELLX 16.2In the following example, prioritization is set for a thirty-channel VoIP connection. The SIP sig-naling port 5060 and the RTP/RTCP ports 29000 to 29059 are prioritized at level 7. All otherservices are set at level 0.Defines the priority of the filter entries.<class> Two types can be set:realtime_class (VoIP packets)regular_class (data packets)<prio> Enter a value between 0 and 15. The higher the value (for example 15), the higher the priority.Filter=<interface> <class> <values>Defines the individual rules for the class.<values> The individual values are divided into the follow-ing entries. A 0 can be entered as a wildcard, in which case all values are possible:<dest_addr> (can be followed by netmask <mask>)<dest_port><src_addr> (can be followed by netmask <mask>)<src_port><protocol tos value>:6 for TCP17 for UDPTable 5.6 Settings in the [altqd] section of the ip.cfg (continued)Interface=<interface> bandwidth <bw> priqExample 5.10 Bandwidth control[altqd]interface pppoe0 bandwidth 512K priqclass priq pppoe0 realtime_class root priority 7 filter pppoe0 realtime_class 0 5060 0 0 0 filter pppoe0 realtime_class 0 0 0 5060 0 filter pppoe0 realtime_class 0 29000 0 0 17 filter pppoe0 realtime_class 0 0 0 29000 17 filter pppoe0 realtime_class 0 29001 0 0 17 filter pppoe0 realtime_class 0 0 0 29001 17 .... filter pppoe0 realtime_class 0 29058 0 0 17 filter pppoe0 realtime_class 0 0 0 29058 17 filter pppoe0 realtime_class 0 29059 0 0 17 filter pppoe0 realtime_class 0 0 0 29059 17 class priq pppoe0 regular_class root priority 0 default

5 Configuration filesPage 46CELLX 16.25.1.9 DHCP server settingsThe DHCP (Dynamic Host Configuration Protocol) server provides a mechanism for allocationof IP addresses to client hosts. The [dhcpd] section contains a list of parameters and settingsfor the DHCP server in the system. It is divided into global settings for the server and param-eters for the DHCP subnet.Table 5.7 Settings in the [dhcpd] section of the ip.cfg [dhcpd]; Global dhcpd parametersallow unknown-clients;All DHCP queries are accepted and the configured settings are transmitted to the clients.ddns-update-style none;Deactivates dynamic update of the domain name system as per RFC 2136.; Parameters for the Subnetsubnet <network address> netmask <mask for network range> {<list>}In <list> you can enter any of the following specific network settings activated by the DHCP server. Each oprion must begin in a new line and end with a semicolon (;).range <start IP address> <end IP address>;The DHCP network range is defined by the first and last address in the range. Client assignment begins with the last address.option broadcast-address <IP address>;Defines the broadcast address for the clients in the subnet.option domain-name "<string>";Defines the domain name used in the network.option domain-name-servers <IP address>;Defines the DNS-server address to be assigned (as per RFC 1035)All of the following optional entries defining server addresses are also transmitted as per RFC 1035. Separate multiple addresses per server with a comma: … <IP address>, <IP address>; (this also applies for all other optional entries with IP addresses).option netbios-name-servers <IP address>Defines the WINS-server address to be assigned.option ntp-servers <ip address>;Defines the NTP-server address to be assigned.option time-servers <ip address>;Defines the time-server address to be assigned (RFC 868).option routers <IP address>;Defines the router address to be assigned.option subnet-mask <net mask>;Defines the netmask to be assigned (as per RFC 950).option tftp-server-name "<link>";Defines the TFTP server name (option 66), as per RFC 2132.EXAMPLE: option tftp-server-name "http://192.168.0.9";

5 Configuration filesPage 47CELLX 16.25.1.10 DNSmasq settingsDnsmasq is an easy to configure DNS forwarder. It is designed to provide DNS to a small net-work.Example 5.11 DHCP server settings[dhcpd]; Global dhcp parametersallow unknown-clients;ddns-update-style none;; Parameter for the Subnetsubnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.3 192.168.1.20; option broadcast-address 192.168.1.255; option domain-name "company.de"; option domain-name-servers 192.168.1.100; option routers 192.168.1.2; option subnet-mask 255.255.255.0;}Table 5.8 Settings in the [dnsmasq] section of the ip.cfg [dnsmasq]bogus-privBogus private reverse lookups. All reverse lookups for private IP ranges (ie 192.168.x.x, etc) which are not found in /etc/hosts or the DHCP leases file are answered with "no such domain" rather than being forwarded upstream.filterwin2kLater versions of windows make periodic DNS requests which don't get sensible answers from the public DNS and can cause problems by triggering dial-on-demand links. This flag turns on an op-tion to filter such requests. The requests blocked are for records of types SOA and SRV, and type ANY where the requested name has underscores, to catch LDAP requests.user=<username>Specify the userid to which dnsmasq will change after startup. Dnsmasq must normally be started as root, but it will drop root privileges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch.cache-size=<cachesize>Set the size of dnsmasq's cache. The default is 150 names. Setting the cache size to zero disables caching.clear-on-reloadWhenever /etc/resolv.conf is re-read, clear the DNS cache. This is useful when new nameservers may have different data than that held in cache.Example 5.12 DNSmasq settingsbogus-privfilterwin2kuser=telescache-size=150cler-on-reload

5 Configuration filesPage 48CELLX 16.25.1.11 PPP configuration for mobile and ISDN dial-upThe point-to-point protocol is used for dial-up connections via GPRS/3G or CMDA, or via ISDNlines. The system can set up an mobile Internet connection for the companies’ local users oran ISDN data link between subsidiaries of the company.The mobile internet access can be used as regular internet access for small companies or asan internet back up solution.The ISDN dial-up can be used to transmit VoIP calls.The advantages of VoIP over ISDN can be seen especially in corporate implementation. Forexample, it is useful when a very high number of connections occurs between subsidiaries andone subsidiary does not have a broadband Internet connection. An ISDN B-channel can beconnected to the Internet and up to six voice calls can occur simultaniously over one ISDN line.All necessary information for setup of the PPP connection is defined in the section [xp-pp<num>].Table 5.9 Settings in the [xppp] section of the ip.cfg [xppp<num>]Dad=<num>Enter the dial-up number. Only digits can be defined here. Any required special characters (* or #) can be set in the mapping entry.User=<username>Enter a username.Pwd=<password>Enter a password.Route=<ip-addr>Enter the target IP address range, for example 0.0.0.0 (default route).AuthProto=<protocol>Enter chap or pap for the protocol used for authentication.AutoUp=<int>Defines if the PPP interface is activated automatically after system start. The following values are possible:0 = No automatic PPP activation (default)1 = Automatic PPP activationIdleTO=<sec>Enter the number of seconds without traffic before the interface tears down the connection.MTU=<int>Maximum Transfer Unit. We recommend the following default values:1500 for ISDN dial-up and 120 for CDMA dial-up.Rfc1662=<val>Framing to be used:0 for ISDN or 1 for CDMALcpTO=<msec>Allows you to change the value of the LCP timeout. The timeout-value must be specified in milli-seconds (default 1000).StartDelay=<sec>Time in seconds the system will wait to start the ppp process.

5 Configuration filesPage 49CELLX 16.2Make sure you configure the firewall and NAT options accordingly.5.1.12 VLAN configurationA VLAN (Virtual Local Area Network) is a virtual LAN within a physical network. Each VLAN isassigned a unique number (VLAN ID) and defined in the [vlan<x>] section with Tag: value between 1 and 4095Priority: value between 0 and 7 (0 is lowest and 7 is the highest priority)[vlan0]IfConfig=vlan <tag>,<priority> vlanif <interface>The following entry will create the interface vlan1, with VLAN tag 10 and priority 7, on theEthernet interface emac0. Following this configuration, IP addresses (and/or other protocols)can be assigned to the vlan1 interface.DNS=<bitmask>Enter here to which of the carrier’s DNS server the gateway shall send the DNS request. The fol-lowing values are possible:1 = primary DNS server2 = secondary DNS server3 = both serversOwnIP=<IP address>A temporay IP address assigned to the interface (such as 0.0.0.0). This address is valid until an IP address has been assigned to the interface by the carrier. Not needed for the xppp0 interface.PeerIP=<IP address>The IP address that is configured for the peer (such as 0.0.0.1). Not needed for the xxxp0 interface, each other interface has to have a different peer IP address.Example 5.13 PPP configuration for ISDN and CDMA dial-up[xppp0]Dad=12345User=userPwd=pwdRoute=0.0.0.0AuthProto=chapIdleTO=60MTU=1500Rfc1662=0LcpTO=500StartDelay=10AutoUp=1Table 5.9 Settings in the [xppp] section of the ip.cfg (continued)[xppp<num>]Example 5.14 VLAN configuration[vlan1]IfConfig=vlan 10,7 vlanif emac0IpAddress=192.168.199.1

5 Configuration filesPage 50CELLX 16.25.1.13 Examples5.1.13.1 Default configurationIn the following example, the system’s IP address is 192.168.1.1, the netmask is255.255.255.0, and the standard gateway is 192.168.1.254.5.1.13.2 Active ethernet bridgeIn the following example a two-port Ethernet bridge is configured. The system’s IP address is192.168.1.1, the netmask is 255.255.255.0, and the standard gateway is 192.168.1.254,The emac1 interface is active and both Ethernet interfaces are set to bridge mode in the[bridge0] section.Example 5.15 Default configuration[System]DefaultGw=192.168.1.254[emac0]IpAddress=192.168.1.1/24Example 5.16 Active ethernet bridge[System]DefaultGw=192.168.1.254[emac0]IpAddress=192.168.1.1/24[emac1]IpAddress=up[bridge0]BrConfig=add emac0 add emac1 up

5 Configuration filesPage 51CELLX 16.25.1.13.3 Integrated DSL-router scenario for VoIPIn the following example, the system is connected to the local IP network through emac0. TheDSL modem is connected to the emac1 interface, which enables the system to connect direct-ly to the Internet without an additional router when the connection is used only for VoIP data.A DHCP server is used for dynamic IP-address allocation.Example 5.17 Integrated DSL-router scenario for VoIP traffic with an active DHCP server and firewall[System][emac0]IpAddress=192.168.0.2/24[emac1]IpAddress=up[pppoe0]PppoeIf=emac1 User=usertelekomPwd=pwdAuthProto=chapRoute=default[nat]map=pppoe0 192.168.0.0/24 -> 0/32 proxy port ftp ftp/tcpmap=pppoe0 192.168.0.0/24 -> 0/32 portmap tcp/udp 40000:60000map=pppoe0 192.168.0.0/24 -> 0/32[firewall]; loopbackfw=pass in quick on emac0 allfw=pass out quick on emac0 all; traffic to outgoingfw=pass out quick on pppoe0 proto tcp all flags S keep state keep fragsfw=pass out quick on pppoe0 proto udp all keep state keep fragsfw=pass out quick on pppoe0 proto icmp all keep state keep frags; incoming trafficfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 21 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 23 flags S keep state keep fragsfw=pass in quick on pppoe0 proto tcp from 10.4.0.0/16 to any port eq 4445 keep state ; icmp trafficfw=pass in quick on pppoe0 proto icmp all keep state; other will be blockedfw=block in log quick on pppoe0 allfw=block out log quick on pppoe0 all[dhcpd]; Global dhcp parametersallow unknown-clients;ddns-update-style none;; Parameter for the Subnetsubnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.3 192.168.1.20; option broadcast-address 192.168.1.255; option domain-name "company.de"; option domain-name-servers 192.168.1.100; option routers 192.168.1.2; option subnet-mask 255.255.255.0;

5 Configuration filesPage 52CELLX 16.25.1.13.4 VLAN scenarioIn the following example, the system is connected to the IP backbone through emac0. OneComputer is connected to the emac1 interface. You can separate voice and data traffic withtwo different VLANs (vlan0 with tag 10 for voice, vlan1 with tag 11 for data). All traffic com-ing from emac1 will be sent to vlan1. Voice and data will not be mixed.5.2 Configuration file pabx.cfgThe pabx.cfg file contains system-specific settings and the port configuration. It is dividedinto the [System] and [Night<num>] sections.5.2.1 System settingsThe [System] section is divided into several categories to ensure clarity. Global settingsLog filesControllersSubscribersIP configurationThe following subchapters contain a detailed description of these categories.5.2.1.1 Global SettingsThe entry in this category is responsible for the life-line (bypass) functionality of the PRI port’srelay when the system is on. When the system is off, both PRI ports are connected to eachother, which means that it provides a transparent connection between the PBX and the PSTNif the system is installed between the PBX and the PSTN. When the system is on, all routingalgorithms are active.Bypass=ON/OFFON: PRI relay is on (system controls both PRI ports).Example 5.18 VLAN scenario[System][emac0]IpAddress=192.168.1.12/16[emac1]IpAddress=up[vlan0]IfConfig=vlan 10,7 vlanif emac0IpAddress=10.0.1.2/24[vlan1]IfConfig=vlan 11,1 vlanif emac0IpAddress=172.16.4.5/16[bridge0]BrConfig=add vlan1 add emac1 up

5 Configuration filesPage 53CELLX 16.2OFF: PRI relay is off (both PRI ports are connected to each other, regardless of whether or notthe system is running).Use the following parameter to configure the system for μ-law coded voice data. Make surethis parameter is set to Yes if you connect your gateway to a T1 line in the U.S.A: Mulaw=yes.5.2.1.2 Log filesCDRs, unconnected calls, system events, trace output and statistics can be saved into files.The following entries are necessary to generate log files: You can define how the log files are to be divided. There are two possibilities for saving entriesinto a new file:In increments of time (twice-daily, daily, weekly, monthly)Depending on the size of the fileYou can also define a maximum number of up to 35 of the most recent files.To ensure bypass functionality, make sure this parameter is always set to ON.iiTable 5.10 pabx.cfg: log file entries Entry DescriptionActionLog=/data/protocol.log System eventsLog=/data/cdr.log CDR entriesfailedlog=/data/failed.log Unconnected callsTraceLog=/data/trace.log System traceMsgLog=/data/msg.log Incoming SMS and USSD messagesThe available internal memory is approximately 8 MB if the does not contain optional memory expansion. Make sure you monitor the available memory.ii

5 Configuration filesPage 54CELLX 16.2A dash (-) appears in place of information that is to be ignored.In the following entry, the files cdr.log and failed.log are renamed every day or when thefile reaches 180kB, whichever comes first. Up to 7 CDR files will be saved on the system. Ifthe file size reaches 180kB on one day, the second file will have the same date. Only the run-ning number will be increased.In the following entry, the file protocol.log is renamed every day or when the file reaches 60kB. Up to 21 failed files will be saved on the system.In the following entry, the file trace.log is renamed every day when the file has reached600kB. Up to seven log files will be saved on the system.Table 5.11 pabx.cfg: log parameters Log=/data/<file.log> <saved> <size> <number><file> The name of the log file is generated as follows: [file]yymmdd[0-9|A-Z].log.<saved> Refers to the frequency with which the file is saved. The following op-tions are possible:halfdaily Every day at 11:59 and 23:59daily Every day at 23:59weekly Sunday at 23:59monthly The last day of the month at 23:59<size> Regardless of the value entered in <saved>, the file will be saved when the <file size> has been reached (in kB).NOTE: We recommend a file size of a multiple of 60kB.<number> Refers to the number of files that will be saved in the system (between 5 and 35) before the first file is overwritten. This setting is useful not only for limited file size, but also for files that store events. Normally size can be limited for these files, for example 5 files of 1MB each. If the fifth file is full, the first one will automatically be overwritten.Example 5.19 Log files renamed 1Log=/data/cdr.log daily 180 7failedlog=/data/failed.log daily 180 7Example 5.20 Log files renamed 2ActionLog=/data/protocol.log daily 60 21Example 5.21 Log files renamed 3TraceLog=/data/trace.log daily 600 7

5 Configuration filesPage 55CELLX 16.2In the following entry, the statistic values are reset daily at 12:00 midnight and saved in theasr.log.5.2.1.3 Night configurationThe sections for the time-dependent configuration changes and time-controlled routings aredefined here. A maximum of 19 additional daily configuration zones are possible (Night1 to Night19). Theentry NightResetTime reactivates the original configuration contained in the System section.The entry will have the following syntax: In the following example, the configuration section is activated Fridays, Wednesdays andMondays at noon unless the day in question is a holiday.Example 5.22 Log files statistic values resetStatisticTime=/data/asr.log 00:00 11111111Please remember to keep track of how much memory is available on the system.iiTable 5.12 pabx.cfg: night parameters Night<num>=<time> <day><num> Enter a value between 1 and 19 to define which configuration is to be loaded.<time> If there is a time set with the format hh:mm after this entry, this configuration is loaded at that time on the defined day. <day> Use a bitmask to set the weekdays on which the configuration applies here. The daymap appears in the following order: HoSaFrThWeTuMoSu.Example 5.23 Night configuration 1Night2=12:00 00101010

5 Configuration filesPage 56CELLX 16.2In the following example, the configuration section switches back to the default configura-tion (System section) every day at 8:00 p.m.HolidaysUp to 50 different dates can be set for night sections used by holiday. The variable dd.mmsets the day and month in which the night section is activated when the 8th bit is set in thebitmask (see Table 5.12).5.2.1.4 ControllersThis category defines the parameters that apply to the ports. The order of the ports is definedas follows: The CELLX contains integrated Mobile Boards, each of which contain four mobilemodules. Each Mobile Board’s mobile channels are configured as additional controllers. Thatmeans four controllers are configured for each board. Beginning with 0, these controllers aredefined as the first controllers in the section. Next the PRI controllers are defined, followed bythe VoIP controllers. All controllers are defined in ascending order. Table 5.13 describes the order for additional boards.Example 5.24 Night configuration 2NightResetTime=20:00 11111111Any defined Night sections must be set in the files pabx.cfg and route.cfg. If there are no changes in these sections, you must copy them from the System section. The complete Sub-scriber section must appear in the Night section of the pabx.cfg (see Chapter 5.2.5 on page 68). The active route(s) (MapAll, Restrict and Redirect entries) must appear in the Night section of the route.cfg (see Chapter 5.3 on page 70).iiTable 5.13 Configuration order: controller parametersFunction Number of ControllersMobile BoardsUp to 32 (optional)Base Board (PRI) 2Base Board (VoIP) Up to 4 (optional)DTMF (virtual) Up to 1 (optional)Table 5.14 shows only the maximum number of controllers for each individual interface. Any possible combinations will depend on the system’s specifications.ii

5 Configuration filesPage 57CELLX 16.2The individual ports are defined with the following parameters.Table 5.14 pabx.cfg: controller parameters Controller<port>=<address> <type> <mode> <line_type> ADR:<hardware address> IRQ:<in-terrupt> UNIT:<unit> VALUE:<value><port> Defines the running (physical) port number.<address> Defines the configured (virtual) port address. In the default configuration, PRI TE ports are 9 and PRI NT ports are 10. VoIP ports are 40.<type> Defines the connection type:TES2M PRI external (terminal endpoint)NTS2M PRI internal (network termination)VOIP VoIP moduleGSM GSM portCDMA CDMA portUMTS UMTS portTE BRI external (if you change from NT to TE or vice versa, you must change the DIP switches for the respective port on the 4BRI Board)NT BRI internal DTMF virtual controller for activating DTMF tone detection<mode> Defines the protocol variation for PRI and BRI lines:DSS1 CASR2 (only for PRI lines)<line_type> Switches CRC4 mode for PRI lines on or off:CRC4 CRC4 onDF double frame: CRC4 offAdditional entry for T1 only:T1 US Defines this controller as T1. Bear in mind that if one con-troller is defined as T1, all controllers must be thus de-fined. If you configure T1, you must also enter CHMAX[23] in the corresponding Subscriber lines.T1 EXAMPLE:MULAW=YesController00=20 TES2M DSS1 T1 US Controller01=21 NTS2M DSS1 T1 US...Subscriber00 = TRANSPARENT ROUTER CHMAX[23]Subscriber01 = TRANSPARENT ROUTER CHMAX[23]ADR:<hardware ad-dress>(Optional) Defines the hardware address used for the first controller on an additional Mobile Board. These entries are preconfigured and cannot be changed.IRQ:<interrupt> (Optional) Defines the interrupt used for the first controller on an addi-tional Mobile Board. These entries are preconfigured and cannot be changed.

5 Configuration filesPage 58CELLX 16.2Ports set to the same type can have the same address. In this case they will form a trunkgroup. If you change this parameter in the configuration, you must restart the system.Each Mobile Board contains 4 controllers. The hardware address and the interrupt are definedbehind the first controllers, which are defined in the configuration before the Base Board. In the following example, the system contains four Mobile Boards. One PRI controller is con-figured for TE and one for NT. The protocol used is DSS1, and CRC4 is active. OneVoIP Module is attached.UNIT:<unit> (Optional) Defines the currency for the charges (default EUR). Special charge generation is possible. Special charge generation is possible for:France UNIT:&FSpain UNIT:&SPPortugal UNIT:&PGreece UNIT:&GSwitzerlandUNIT:&CHNetherlandsUNIT:&NLItaly UNIT:&INOTE: The <line_type> must be configured for these entries to work. EXAMPLE: Controller02=10 NT DSS1 PMP UNIT:€ VALUE:0.010Controller03=10 NT DSS1 PMP UNIT:€ VALUE:0.010VALUE:<value> (Optional) Defines the charges that accumulate by unit (default 12).Table 5.14 pabx.cfg: controller parameters (continued)Controller<port>=<address> <type> <mode> <line_type> ADR:<hardware address> IRQ:<in-terrupt> UNIT:<unit> VALUE:<value>Example 5.25 Controller settings 1Controller00=20 GSM ADR:D800 IRQ:5 Controller01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSM ADR:D900 IRQ:7 Controller05=20 GSMController06=20 GSMController07=20 GSMController08=20 GSM ADR:DA00 IRQ:5Controller09=20 GSMController10=20 GSMController11=20 GSMController12=20 GSM ADR:DB00 IRQ:7Controller13=20 GSMController14=20 GSMController15=20 GSMController16=9 TES2M DSS1 US DFController17=10 NTS2M DSS1 US DFController18=40 VoIP

5 Configuration filesPage 60CELLX 16.2Required mobile parametersSpecific settings for each mobile interface appear in square brackets behind the keywordsGSM, UMTS or CDMA. These parameters are separated with a comma. Example 5.26 Subscriber settings 1Subscriber00=TRANSPARENT ROUTER ALARMSubscriber01=TRANSPARENT ROUTER ALARMSubscriber02=TRANSPARENT ROUTER SWITCH CHMAX[16] ALARMTable 5.16 Required mobile parameters in pabx.cfg Subscriber<port>=<type>[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM<x>,...]<port> Refers to the running (physical) port number.<type> Enter GSM, CDMA or UMTS depending on your hardware configuration.<pin> Defines the SIM card’s PIN. The PIN is always four digits. If no PIN is defined for a SIM card, the PIN 0000 must be used.NOTE: An error message appears in the protocol.log file when a PIN is incorrectly configured.<lain> Defines the LAIN (Local Area Identification Number) – the mobile network to be used. The LAIN consists of the MCC (Mobile Country Code) and the MNC (Mobile Network Code). Setting this parameter prevents roaming into another mobile network. If the LAIN is set at 00000, roaming will not be prevented. The LAIN configuration prevents accidental logon of the SIM card with another net-work and the use of false SIM cards.<SMSC> Defines the SMS center’s access number. The number must always begin with + and the country code.<SIM> Defines the SIM card to be used. You can enter the values 1, 2, 3, 4, 5, 6 (op-tional when using the 24 SIM card carrier). Default 1. Do not change the de-fault entry if your gateway is equipped with SIM4 carriers . Activate configuration suffices to activate changes.NOTE: Please see the example following Table 5.17 for information on numbering SIM cards.<loudGSM> Defines the volume level for the mobile line. The values 0 to 3 are possible. 0 is loudest and 3 is the least loud.Activating echo cancellation (for GSM modules only):Depending on the base station (BTS) one of three algorithms will work for this feature. The algorithms must be tested during activation to determine which one fits the base station type.The following values are added to the volume setting:- 16 -> algorithm 1 - 32 -> algorithm 3 - 48 -> algorithm 6 EXAMPLE 1: If the volume level is set at 1, and algorithm 1 is used for echo can-cellation, the configuration for <loudGSM> is 17:Subscriber00=… GSM[0000,00000,+000000,1,17,1,SIM4] …EXAMPLE 2: If the volume level is set at 2, and algorithm 6 is used for echo can-cellation, the configuration for <loudGSM> is 50:Subscriber00=… GSM[0000,00000,+000000,1,50,1,SIM4] …

5 Configuration filesPage 61CELLX 16.2Optional mobile parametersIn addition to the usual parameters, you can enter the following optional mobile parameters.Separate each parameter with a comma. <loudPCM> Defines the volume level to the fixed network. The values 0 to 7 are possible. 7 is loudest and 0 is the least loud.SIM4 Indicates that the gateway is equipped with SIM4 carriers. Table 5.16 Required mobile parameters in pabx.cfg (continued)Subscriber<port>=<type>[<pin>,<lain>,<SMSC>,<sim>,<loudGSM>,<loudPCM>,SIM<x>,...]Table 5.17 Optional mobile parameters in pabx.cfg Parameter DescriptionBAND(<int>) Defines the GSM frequency band and (<int>) can have the following values:1 = Mono-band mode 850MHz (Q24CL001 modules only)2 = Mono-band mode 900MHz (Q24CL001 modules only)3 = Mono-band mode 1800MHz (Q24CL001 modules only)4 = Mono-band mode 1900MHz (Q24CL001 modules only)5 = Dual-band mode 850/1900MHz (Q24CL001 and GE864-QUAD modules)6 = Dual-band mode 900/1800MHz (Q24CL001 and GE864-QUAD modules)7 = Dual-band mode 900/1900MHz (Q24CL001 and GE864-QUAD modules)8 = Dual-band mode 850/1800MHz (GE864-QUAD modules only)After changing the band settings, you must restart the system to activate the changes.NOTE: The BAND parameter can only be used with quad-band GSM module-type Q24CL001. These quad-band GSM modules are avail-able as of hardware revision 1.61 (May, 2007). There is no default band setting! If there is no BAND configuration in the pabx.cfg when the system is started, the last band stored on the module will be used. This can cause the system to attempt to register the SIM with the wrong GSM band.BNDS<int> For UMTS Boards with module type UC864-G only:Selects the UMTS or GSM or auto network0 = auto (default)1 = GSM2 = UMTS BNDU(<int>) For UMTS Boards with module type UC864-G only:Configures BAND selection in the UMTS network0 = 850/1900/2100 MHz (default)1 = 850 MHz2 = 1900 MHz3 = 2100 MHz

5 Configuration filesPage 64CELLX 16.2NtpServer=<ip addr>Sets the SNTP server’s IP address for standard-time queries. The query occurs every four hours.NOTE: If your system is not attached to an NTP server, you can enter the following config-uration to retrieve the time from an ISDN TE port:Subscriber=...TIMEClockmaster=<type>Enter S0 to take the system clock from the BRI port if the system has an additional BRI board and special firmware installed on which at least one controller is connected to the PSTN in TE mode. This parameter only makes sense if the system does not have a PRI port connected to the PSTN.S2MLongHaul=<mode>This option increases the sensitivity on PRI receiving side to support Long Haul applications. The default value is No (Short Haul).MoipPort=<port>Defines the GATE Manager access port (default 4445).FtpdPort=<port>Defines the FTP access port (default 21).TelnetdPort=<port>Defines the TELNET access port (default 23).TftpdPort=<port>Defines the TFTP access port (default 69).Ftpd=<mode>Activates (on) or deactivates (off) FTP access. Default on.Telnetd=<mode>Activates (on) or deactivates (off) TELNET access. Default on.Tftpd=<mode>Activates (on) or deactivates (off) TFTP access. Default off.RemotePassword=<password>Defines the password for FTP and GATE Manager access. Please refer to Chapter 4.10.4 on page 34 for instructions on how to enter an encrypted password in the pabx.cfg. If you do not define a password, access to the system via GATE Manager occurs without a password, and FTP access occurs with the default password tcs-ag. DialTone=<country>If the system is used in a corporate settings and attached through a PBX to the PSTN, it may be necessary to generate the carrier’s dial tone. It depends on whether the system sends the dialed digits to the PSTN or whether it waits for a routing entry to take the call.The following values can be entered: GE, DE, IR, UK, US, FR, ITExample 5.27 Global settingsVoipGlobalMaxChan=60H225Port=1720SipPort=5060VoipRtpPort=29000VoipRtpPortSpacing=2NameServer=192.168.0.254Timezone=Europe/BerlinNtpServer=192.168.0.254DialTone=GETable 5.18 pabx.cfg: global settings (continued)System Parameters

5 Configuration filesPage 65CELLX 16.25.2.2 SMTP-client configurationThe following entries in the pabx.cfg’s [Mail] section are used to send e-mail messages fromthe CELLX. The connection to the SMTP server can be used to send CDR files, incoming SMSto an e-mail account or alarm messages.The following features are possible:Sending SMS via e-mailReceiving SMS in an e-mail, SMS or in a fileSending and receiving USSD text messagesDisplaying incoming calls via e-mailSetting up connections using e-mailSending automatic SMS for unconnected callsSending CDRs via e-mailSending alarm messages via e-mailThere is no internal time generation for the system when the power is interrupted. That means the default time is used when the system is restarted or rebooted! Therefore it is important to set the system time with an NTP server. Alternatively, 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.cfg’s subscriber line of the TE port and then activate the configuration to activate this clock.iiYou must restart the system after making changes to activate the settings.iiTable 5.19 SMTP client configuration SMTP parametersSmtpServer=<ip addr>In <ip addr>, enter the IP address of the destination SMTP server that is to receive the e-mail messages. MailUserIn=<username>Enter a username for incoming e-mail authentication.MailUserOut=<username>Enter a username for outgoing e-mail authentication.MailPwdIn=<password>Enter a password for incoming e-mail authentication.MailPwdOut=<password>Enter a password for outgoing e-mail authentication.MailPortIn=<num>Enter a TCP port for incoming email (default 25).MailPortOut=<num>Enter a TCP port for outgoing email (default 25).MailAuthEncr=<type>Enter an encryption method for e-mail authentication (default base64).

5 Configuration filesPage 66CELLX 16.2Sending alarm messages via e-mailWith the appropriate configuration, you can send e-mails containing alarm messages that arewritten into the log file. The sender is given as alarm and the system’s name appears in thesubject box. The text box contains the alarm message. MailRcpt=<domain>In <domain>, enter the destination domain, the destination address and an @ sign. If the desti-nation address is already complete (with an @ sign), <domain> is not added.MailFrom=<URL>Enter here the URL that will be sent in the e-mail’s FROM field in the following possible formats: MailFrom=domain to send OAD@domain (or user@domain, if no OAD available).MailFrom=ipaddress to send OAD@ipaddress (or user@ipaddress, if no OAD available).MailFrom=123@ to send 123@<IP address of gateway>.MailFrom=123@teles.de to send 123@teles.de.MailFrom=123@ipaddress to send 123@ipaddress.MailRcvMax=<count>Maximum number of incoming e-mails queued for transmission via SMS or USSD.MailRcptMax=<count>Number of "RCPT TO" entries in e-mails that come from the LAN (a message is sent to the LCR for each "RCPT TO" entry in each incoming e-mail).MaxMailsToHost=<count>Maximum number of e-mail messages sent to the LCR simultaneously. Default 4MailToHostRetries=<count>Number of retries when SMS transmission is not successful. When the limit entered is reached, an error message is sent to the e-mail sender (default 3).MailSendRetries=<count>Number of times an attempt is made to send an e-mail. Default 10.MailMaxIncomingClients=<count>Defines the maximum number of clients that can access the system simultaneously. If 0 is entered, the SMTP port (25) will be blocked for incoming sessions. Default 100.MailTcpRcvTimeout=<sec>Defines the number of seconds after which a session will be terminated following a possible re-ceiving error in the data stream. Default 0 (immediately).MailTcpSndTimeout=<sec>Defines the number of seconds after which a session will be terminated following a possible transmission error in the data stream. Default 0 (immediately).MailAllowedPeers=<ip addr>Defines IP addresses from which incoming SMTP connections will be accepted. Separate IP ad-dresses with a space. If a dash (-) is entered, the SMTP port (25) will be blocked for incoming ses-sions. If this parameter is left empty (default), incoming connections will be accepted from all IP addresses.MailPropPort=<num>Enter the port number for a TELES proprietary mail protocol.Table 5.19 SMTP client configuration (continued)SMTP parameters

5 Configuration filesPage 67CELLX 16.2The following entry in the configuration file activates this function.5.2.3 Number portability settingsThe [NumberPortability] section includes the parameters necessary for communication withthe database server. For a description of the functionality and configuration of this feature,please see Chapter 11.5 Ported number screeningExample 5.28 Sending alarm messages via e-mai...ActionLog=/data/protocol.log daily 1000 5 @<e-mail account>...You must restart the system after making changes to activate the settings.Table 5.20 Number portability settings Number portability parametersMNPQAddress=<ip addr>For iMNP or direct queries to Enquire: Enter the IP address to which the number portability query is to be sent.MNPQPort=<port>For iMNP or direct queries to Enquire: Enter the tcp port to which the number portability query is to be sent.MNPQAddress2=<ip addr>For iMNP or direct queries to Enquire: Enter the IP address to which the second number portability query is to be sent when ! appears in the mapping entry. A second database will then be queried, for example if the first one is not online.MNPQPort2=<port>For iMNP or direct queries to Enquire: Enter the tcp port to which the second number portability query is to be sent.MNPQSum=<mode>For iMNP: This parameter must be activated (Yes) if an iMNP is used.E2EMRSAddress=<ip addr>For direct queries to End2End: Enter the IP address to which the number portability query is to be sent.E2EMRSPort=<port>For direct queries to End2End: Enter the udp port to which the number portability query is to be sent. ii

5 Configuration filesPage 71CELLX 16.2The Restrict parameter adds a prefix to a DAD before the DAD is mapped. Restrict pa-rameters are always handled before the MapAll parameters and always require a matchingMapAll parameter.The left side of the equals sign in the Restrict parameter contains the controller numberplus an optional trunk number or a specific calling number (OAD). The special symbol ? maybe used as a wildcard to represent any character. The right side contains the prefix that is tobe put in front of the DAD and an optional service indicator.In the route.cfg, the list of Restrict parameters is searched from bottom to top for amatching controller plus optional trunk number / OAD. Because the search is done bottomup, place the more specific Restrict entries below the more general ones. Once a matchhas been found, the DAD is prefixed with the contents of the <pl> variable. Then the call ismapped.Table 5.23 route.cfg: restrict parameters Restrict<ns>[R][T]=<pl> <sin>Parameter Description No. Digits Optional<ns> Contains the controller number plus an optional trunk number or a specific calling number (OAD). The special symbol ? may be used as a wildcard to represent any character. 59[R] For calls that are redirected with Redirect3, the original OAD can be changed again using RestrictR. Only in combination with service indica-tor 15.X[T] For calls that are redirected with Redirect2, the original OAD can be changed again using RestrictT. Only in combination with service indica-tor 15.X<pl> Stands for a virtual placeholder. The DAD is prefixed with the contents of this variable.59<sin> The service indicator variable sin restricts the com-mand to a service. Without a sin, the Restrict com-mand is valid for all services.Possible service indicator values are:00 All services01 Telephony02 Analog services03 X.21-services04 Telefax group 405 64 kbps videotext or TELES-specific SMS services06 TELES-specific USSD services07 Data transfer 64 kbps08 X.25-services09 Teletext 6410 Mixed mode15 Used internally for calling-party (OAD) manipulation.16 Video telephone2

5 Configuration filesPage 72CELLX 16.2All calls from PRI controller 9 (PSTN) are sent to PRI controller 10 (PBX). First, the Restrict com-mand adds the prefix “pl” to the DAD of the received call for all calls coming from PSTN. Thenthe call is mapped. In the mapping, everything that is prefixed with “pl” is sent to controller10 by removing the prefix and adding the controller to the number.Calls from mobile controllers with the LAIN 26212 are sent to PRI controller 10 (PBX), exten-sion 0. This is imperative because the caller cannot dial an extension directly with mobile.For a detailed description, please see Chapter 7.2 Incoming voice calls from mobile.5.3.1.2 MapAllMapping entries are necessary for routing calls. The prefix or telephone number (DAD) forwhich the mapping applies is searched and the call routed according to the matching map-ping entry.Mapping entries begin with the keyword MapAll. They work as follows: anything on the leftof the equals sign is removed from the prefix / telephone number (DAD) that has come in andreplaced with what is on the right of the equals sign.If, for example, the incoming DAD is 12345678 with 123456 being the trunk number and 78the extension, MapAll123456=9123456 means that 123456 is cut off the number and9123456 is added to it. The called number is 912345678 with 9 being the port.MapAll123456=9 means that 123456 is cut off and 9 added. The called number is 978 with9 being the port.Example 5.30 Restrict 1Restrict9=plMapAllpl=10Example 5.31 Restrict 2Restrict26212=100

5 Configuration filesPage 74CELLX 16.25.3.1.3 RedirectThis entry facilitates alternative routing when the first destination cannot be reached or isbusy. A placeholder appears to the right of the equal sign. The routing entry (MapAll) can bedefined for the redirect using the placeholder entered.Make sure that the numbers for the carriers are routed to the correct ports! For detailed in-formation on digit collection and enblock/overlap receiving, please see Chapter 8.4 Digit col-lection (enblock/overlap receiving).iiTable 5.25 route.cfg: redirect parameters Redirect<type><num>=<redirect> <sin> <time>Parameter Description No. Digits Optional<type> Enter 2 or 3 to set the following types:2call forwarding no answer3call forwarding when busy1<num> Defines the number for which calls will be redirected. 59<redirect> Defines the placeholder used in the two-target routing entry and the number to which calls to <x> will be redi-rected. 59<sin> The service indicator variable sin restricts the command to a service. Without a sin, the Redirect command is val-id for all services.Possible service indicator values are:01 Telephony02 Analog services03 X.21-services04 Telefax group 405 Videotext (64 kbps)07 Data transfer 64 kbps08 X.25-services09 Teletext 6410 Mixed mode15 Videotext (new standard)16 Video telephoneNOTE: Fax forwarding must be set for analog and telephony services because incoming fax calls from the analog network may arrive with either telephony or analog service indicators.2(X)(Only op-tional if <time> is not set. If <time> is set and <sin> is not need-ed please select 00 for sin.)<time> For type 2 redirect entries, a timer (in seconds) can be defined after the service indicator entry.255 X

5 Configuration filesPage 75CELLX 16.2In the following example, all mobile calls with the prefix 01555 are transmitted to the mobilecarrier with the LAIN 26212. Digit collection is activated. If the carrier cannot be reached oris busy, the redirect command activates the second target mapping with the placeholder Aand the call is automatically sent to PRI controller 9.In the following example, calls to 26212 that remain unanswered for 12 seconds and calls to26213 that remain unanswered for 20 seconds are redirected through the PRI port.Excluding busy calls or specific cause values from redirectDefines a hexadecimal cause value according to DSS1. When connections to the destinationare rejected because of the reason defined by the cause value, the CELLX sends a busy signalto the attached PBX. Alternative routing is not carried out.To avoid second-choice routings when the called-party number is busy, set the following pa-rameter in the first-choice port’s Subscriber line in the pabx.cfg:BUSY[<cause>]Defines a hexadecimal cause value according to DSS1. When connections to the destinationare rejected because of the reason defined by the cause value, the CELLX sends a busy signalto the attached PBX. Alternative routing is not carried out. You can also define a range ofconsecutive cause values: BUSY[<cause>,<cause>]An exclamation point (!) in front of a cause value means all cause values except the one listed.For example, BUSY[!95], means all cause values except 95 will be rejected with a busy signal.In the following example, all outgoing calls over controller 04 are rejected with the cause val-ue 91 when the called party is busy. Alternative routing is not carried out.5.3.1.4 Setting the time-controlled sectionsIf you use a time-configured route on the system, please see Chapter 5.2.1.3 for a definitionof individual configuration zones. The active route is configured in the route.cfg file.Example 5.34 Redirect 1MapAll01555=|2621201555<<17Redirect326212=AMapAllA=9Example 5.35 Redirect 2MapAll01555=|2621201555<<17MapAll01556=|2621301556<<17Redirect226212=A 01 12Redirect226213=A 01 20MapAllA=9Example 5.36 Called party is busySubscriber04=....BUSY[91]

$5 Configuration filesPage 79CELLX 16.25.3.3 Gatekeeper profilesGatekeeper profiles are used to connect the CELLX to several systems by using a gatekeeperif the protocol is H.323. It is possible to configure different gatekeepers for different destina-tions and to define backup gatekeepers. These gatekeeper profiles are then assigned to theVoIP profiles.VoipIpLogging=<mode>Enter Yes to activate recording IP addresses in the CDRs (default is No). The first IP address is the signaling address and the second is the RTP address, followed by the the codec and the frame size used. The IMSI appears after the IP addresses if the keyword IMSI is defined in the pabx.cfg.Example of a CDR entry:21.08.07-11:01:42,21.08.07-11:01:58,40,912345,192.168.0.2:192.168.0.2,G729,10,0101,16,10,0Example of a failed log entry:21.08.07-11:11:30,40,91234,192.168.0.2:192.168.0.2,G729,10,0101,ff,2,1VoipStatLogging=<mode> When Yes is entered, statistic values (for example fraction lost, round trip time, and so on) for the VoIP profile are saved into the protocol.log file every ten minutes. This is helpful during problem analysis when IP issues occur (default = No).VoipHold=<mode>Determines the behavior of the HOLD feature if a PBX sends an Re-INVITE message for HOLD to the gateway.transparent: HOLD is sent to PSTNnotify: HOLD is sent as notification to the telephone exchangeignore: HOLD is not sent to the telephone exchange - the gateway suppresses the messages to PSTNVoipSelectProfilesBySignalling=<Yes/No>When Yes is entered, VoipSignalling=<int> is taken as the criterion for selecting a voip-profile for an incom-ing voip call, i.e. the signalling for this voip call must match the VoipSignalling param-eter in this profile. Default No.Table 5.27 route.cfg: VoIP management parameters (continued)VoIP Management ParametersTable 5.28 route.cfg: gatekeeper parameters Gatekeeper Parameters[Gatekeeper:<name>]Name of the gatekeeper profile.RasPort=<port>Indicates the port the gatekeeper uses (default 1719) for registration, admission and status.OwnRasPort=<port>Indicates the port the system uses (default 1719) for registration, admission and status.RasPrefix=<list>CELLX’s defined prefix(es). Use a space to separate entries.RasId=<name>The alias used for gatekeeper registration.GkId=<name>The gatekeeper’s alias.$

5 Configuration filesPage 82CELLX 16.2User=<name>Enter a username for authorization.Password=<password>Enter a password for authorization.Secret=<secret>Enter the shared secret.OwnId=<name or ip addr>Host name or IP address used in the NAS identifier or NAS IP address (Cisco VSA gateway ID).ServiceType=<num>As defined in RFC 2865, Chapter 5.6.RequestTimeout=<sec>Number of seconds during which the request is repeated if the Radius server does not respond.RequestRetries=<count>Number of packet retries sent at one time.StopOnly=<mode>When yes is entered, only Accounting Request Messages with the status type stop are transmit-ted to the Radius server.AlwaysConnected=<mode>Enter No (default) to set the value for the field ConnectedTime to that of the field Disconnect-edTime in accounting-stop messages when the call was not connected.CallingStationId=<num>This parameter is used to set the calling station ID. The default setting is the OAD, but you can define any calling station ID. To define a partial calling station ID, enter a ? for each digit. For ex-ample, CallingStationId=??? will consist of the first three digits of the OAD.CallType=<int>Enter one of the following to define the call type:3 = VoIP and telephony2 = VoIP only1 = Telephony onlyFramedProtocol=<int>Enter one of the following to define the framed protocol (see RFC 2865, Chapter 5.7):1 = PPP2 = SLIP3 = AppleTalk Remote Access Protocol (ARAP)4 = Gandalf proprietary SingleLink/MultiLink protocol5 = Xylogics proprietary IPX/SLIP6 = X.75 SynchronousNasId=<string>The string entered is used as network access server identifier attribute in access requests. If no string is entered, the attribute will not be set (default).Table 5.30 route.cfg: radius parameters (continued)Radius Parameters

7 Mobile configuration optionsPage 88CELLX 16.27.1 Network-specific mobile routing7.1.1 Routing decisions for calls to the mobile networkInternal routing decisionsUsually, routing decisions are made internally by the gateway. Calls to the mobile networkare routed based on the first digits of the called destination number (mobile network accessnumber) via a port or LAIN. The mapping looks like this:MapAll<mobile network access number>=<port/LAIN><mobile network accessnumber> In the example shown below, calls to the mobile network access number 0172 are routed viaport 20. In the example below, calls to 0176 are routed via the LAIN 26227. To route via LAIN, thekeyword CHADDR needs to be added to the mobile port’s Subscriber configuration.External routing decisionsIn some cases, the routing decision needs to be made before the call arrives on the gateway.This can be done by adding a technical prefix to the called number.Each prefix represents a national mobile network. For instance 7777# could be the prefix toroute calls to the LAIN 26222, 8888# could route calls to the LAIN 26227.If a call to the mobile network arrives on the gateway containing a technical prefix, this prefixneeds to be removed in the MapAll parameter and replaced by the port or LAIN. The config-uration is:MapAll<technical prefix>=<port/LAIN>The mapping can be extended to contain the mobile network access number.MapAll<technical prefix><mobile network access number>=<port/LAIN><mobilenetwork access number>In the following example, calls containing the prefix 7777# are routed via port 20. Calls con-taining the prefix 8888# are routed via port 21.Example 7.1 Internal routing decision 1MapAll0172=200172Example 7.2 Internal routing decision 2MapAll0176=262270176Example 7.3 External routing 1MapAll7777#=20MapAll8888#=21

7 Mobile configuration optionsPage 89CELLX 16.2In the following example, calls which come in with the prefix 9999# and the mobile networkaccess number 0176 are routed via the LAIN 26227 to 0176.7.1.2 Using the LAIN as the mobile port addressUse the LAIN as controller with the CHADDR parameter to prevent logging onto the wrongSIM card. This will ensure that routing is network specific. The following example is based onthe German country code. One carrier’s LAIN is 26212 and the other carrier’s LAIN is 26213.Example 7.4 External routing 2MapAll9999#0176=262270176Example 7.5 Using the LAIN as the mobile port address (pabx.cfg)...Controller00=20 GSMController01=20 GSMController02=20 GSMController03=20 GSMController04=20 GSMController05=20 GSMController06=20 GSMController07=20 GSM...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber01=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber02=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber03=TRANSPARENT ROUTER GSM[0000,00000,+49556,1,1,1,SIM4] CHADDR ALARMSubscriber04=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber06=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARMSubscriber07=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR ALARM...If you remove the keyword CHADDR from the pabx.cfg, you must restart the system. Control-lers belonging to the same trunk group must have the same address. You must delete all rout-ing entries based on port addresses when using the LAIN as controller.Example 7.6 Using the LAIN as the mobile port address (route.cfg)...MapAll01555=2621201555...MapAll01556=2621301556...ii

7 Mobile configuration optionsPage 90CELLX 16.27.1.3 Fixed LAIN for a mobile portEnter CHADDR[<addr>] to remove a mobile controller belonging to an LAIN group from thestandard routing process (for example for specific routes or only for SMS transmission). Theport address can be set to <addr>.7.2 Incoming voice calls from mobileIncoming mobile calls (service indicator 01 represents voice calls) can be routed to a specifiednumber. This enables each mobile controller to receive a unique identifier. It will then bemapped to a number.The mobile controllers can also have the same identifier, so that all voice calls (service indica-tor 01) from controller 20 are sent to number 1111 at port 9. This number could, for example,serve a call center.7.3 Blocking portsThis function allows you to block a port, so that the corresponding mobile channel is omittedfrom the distribution of calls. The function is particularly useful when mobile channels fail orSIM cards cannot be immediately replaced. To disable the port for outgoing calls enter the keyword CHINC[01,01] in the Subscriberline and restart the system. In the following example, port 04 is blocked for outgoing calls.Example 7.7 Fixed LAIN for a mobile portSubscriber05=TRANSPARENT ROUTER GSM[0000,00000,+49555,1,1,1,SIM4] CHADDR[444] ALARMMapAllSMS=444 DATAThe value entered for <addr> may not exceed 6 digits.iiExample 7.8 Incoming voice calls from mobile 1Restrict20=90123 01Restrict21=91234 01Example 7.9 Incoming voice calls from mobile 2Restrict20=91111 01

7 Mobile configuration optionsPage 92CELLX 16.27.5 Optional mobile quality parametersThe following parameters can be set for specific carriers if SIM cards for different mobile net-works are used and different configurations must be set.For all controllers without a LAIN, the following default setting applies: GSM=Up to four additional carrier-specific entries may be set:GSM1=<Lain1> ALFI[<val1/val0>]...GSM2=<Lain2> ...GSM3=<Lain3> ...GSM4=<Lain4> ...Up to four LAIN-specific configurations are possible. The user must enter the index (1 to 4).The LAIN appears as the first entry behind the equal sign. Everything else follows.The following table describes specific signaling and quality parameters for configuration ofthe mobile interface. Make sure that no Restrict entries are configured for these mobile controllers.iiBear in mind that for iGATE UMTS you must use the keyword UMTS= instead of GSM=!The following syntax applies: UMTS1=<Lain1> ALFI[<val1/val0>]...iiThere is no automatic default behavior for this feature! All options must always be entered. We recommend that you enter GSM= settings, as all controllers without a LAIN or with a de-fault address use these options!iiTable 7.1 Optional mobile parameters GSM=... (for iGATE GSM) or UMTS= … (for iGATE UMTS)Enter any of the following parameters after the equal sign for the following functions. Entries may appear in any order, but all entries must appear in the same line and in double-digit notation as fol-lows:GSM=RSSI[10] STOP[18,08] ANNOUNCE[00,08] FAX[a2] ASR[20,35]or UMTS=RSSI[10] STOP[18,08] ANNOUNCE[00,08] FAX[a2] ASR[20,35]ALERT[<sec>] Set this parameter to generate an alert signal in the D channel im-mediately after the dial-end signal. If you enter optional square brackets containing a number of seconds, the alert signal will oc-cur when the number entered has passed following setup.

7 Mobile configuration optionsPage 93CELLX 16.2ANNOUNCE Set this parameter to define what happens when a recorded an-nouncement is detected:No ANNOUNCE entry (default)A D-channel PROGRESS message stating Inband Information Available will be generatedANNOUNCE[<cause>]The connection will be rejected with the defined ISDN cause value. Do not enter the cause value ff!ANNOUNCE[00,<sec>]A timeout for voice detection is defined in seconds (default value: 120 seconds). After the interval entered has passed, the connection is torn down.ANNOUNCE[ff]The call will be connected as soon as an announcement is de-tected.FORWARD[<cause>] For GE864-QUAD modules onlyThe connection will be rejected with the defined ISDN cause value when call forwarding is detected.NOTE: The GSM network must support this feature for it to work.ASAL Announcement Stop during ALert: Set this parameter to release calls if the GSM network sends an alert message, after which voice is detected (for example the B-party rejects the call, which is then forwarded to the B-party’s voicemail following the ring state).The parameter ANNOUNCE[<cause>] must be set to activate this parameter.MINV[<count>] Minimum Voice detections: Parameter used with ASAL to define the number of voice detections in a row before the call is released (for example GSM-network background noise detected as voice). The default value is 1, but 2 is recommended.The parameters ANNOUNCE[<cause>] and ASAL must be set to activate this parameter.ASR[<limit>,<calls>]Allows you to change the default value (40 calls at 30% ASR). For a definition of ASR, see Chapter 11.4.1 Generating and retrieving CDRs.CDC[<seconds>,<count>]Call duration check. When more than (<count>) connected calls in a row occur with a call duration lower than <seconds>, an alarm is generated and the port is restarted.FAX[<cause>] This entry allows you to reject fax calls with the defined cause val-ue.RSSI[<limit>] Configure this parameter to set a limit for the reception field strength. When the reception field strength falls below this limit, the mobile channel will be blocked. If the field strength is above the limit, the mobile channel will log on with the mobile carrier again. The values used are 0 to 31, which represent the following field strengths: -113dBm to -51 dBm. An error is generated in the protocol log. The result must be divided by 2.EXAMPLE: To define a field strength of -95 dBm, subtract -95 from-113 and divide the result by 2:- 113dB - (-95dB) = -18dB / 2 = 9Enter RSSI[9]Table 7.1 Optional mobile parameters (continued)GSM=... (for iGATE GSM) or UMTS= … (for iGATE UMTS)

7 Mobile configuration optionsPage 94CELLX 16.2STOP[<val1>,<val2>]This entry allows you to define a maximum number of connection setups that always result in a recorded message (<val1>) without an alert detection or call-connected signal. The second value (<val2>) counts calls that connect immediately without an Alert detection. The mobile port is blocked when the defined value is reached and an entry is recorded in the log file (...Err: Voice). In this way inactive SIM cards that are forwarded to a recording (with or without a connect from the mobile carrier) can be detected and blocked so that they are removed from the routing process. The default status of this function is off.NOCP When this option is configured and the call is from ISDN to GSM, the Call Proceeding signaling message will be eliminated from sig-naling. This may be necessary if the ISDN peer does not support Call Proceeding. Bear in mind that the peer’s Setup Ack Timer is usually set at 5 seconds, which means that an Alert must be gen-erated as follows: GSM=ALERT[5] (for iGATE GSM)UMTS=ALERT[5] (for iGATE UMTS)FMIN[xxx] FMAX[yyy] Sets the frequency range for ringtone detection (default 400-444 Hz).EXAMPLE:GSM=FMIN[400] FMAX[444] (for iGATE GSM)UMTS=FMIN[400] FMAX[444] (for iGATE UMTS)ALFI[<val1/val0>] GSM module GE864-QUAD only. Switches the digital filter on (val=1) the Telit module to suppress frequencies below 250 Hz per LAIN during alerting. (switch off val=0)Please use the parameter to enable alert-tone detection for dual tone LAINs only (please see Chapter 7.5 Optional mobile quality parameters).VOICE[<sec>] The voice channel in the switching matrix is connected after <sec> (default immediately). The voice channel is activated no later than the point at which the call is connected.WND9 Voice detection is activated in the GSM module if the GSM net-work signals WND9 (voice). If this parameter is not set, voice de-tection is activated immediately when the GSM call is initialized.Module Q24xx only.WND2A Generates Alert when WIND:2 is received. Module Q24xx only.WND2N Suppresses voice detection after WIND:2 is received. Module Q24xx only.MINA[<count>] Defines the number of alert tones that are required before an Alert is detected.Table 7.1 Optional mobile parameters (continued)GSM=... (for iGATE GSM) or UMTS= … (for iGATE UMTS)

7 Mobile configuration optionsPage 95CELLX 16.27.6 Deactivating mobile rerouting Use the following entries in the pabx.cfg to deactivate rerouting for rejected calls.REDIAL[<percent>,<waitmin>,<waitmax>,<callingmin>,<callingmax>,<connectmin>,<connectmax>,<cfg>]Repeats a call to the same B-party number as soon as the A party hangs up. This parameter is useful for improving call statistics:Percent: Percentage of calls (including alert only)through the gateway that are redialed.Waitmin: Minimum number of seconds thegateway waits before redial.Waitmax: Maximum number of seconds thegateway waits before redial.Callingmin: Minimum number of seconds thegateway waits before call setup for redial. Werecommend no more than 8 seconds.Callingmax: Maximum number of seconds thegateway waits before call setup for redial. Werecommend no less than 15 seconds.Connectmin: Minimum connect time (in seconds) ifcall is connected.Connectmax: Maximum connect time (in seconds)before call is disconnected.Cfg: Enter a value 1 – 4; valid for the 1= line to 4= linefor the iGATE GSM, or for the 1= line to 4= line forthe iGATE UMTS. CPSA[0|1] When CPSA ist set to 0, the GSM port is forced to register the SIM card to it’s home network, which is identified by the first 5 or 6 digits of the IMSI. This may result in a faster registration process. CPSA[1] is the default value.Table 7.1 Optional mobile parameters (continued)GSM=... (for iGATE GSM) or UMTS= … (for iGATE UMTS)Table 7.2 Deactivating mobile rerouting ParametersAllClassNext=<mode>Enter AllClassNext=Off to deactivate rerouting for all rejected calls, regardless of the cause value (default not configured).NOTE: You cannot configure both AllClassNext and Class2Next simultaneously!Class2Next=offEnter Class2Next=Off to deactivate rerouting for calls rejected with a class 2 cause value (default not configured).NOTE: You cannot configure both AllClassNext and Class2Next simultaneously!SelfNext=<int>Set this parameter to reroute a failed call through the same port. <int> defines the number of call attempts. Recommended values for <int> are 2 or 3. Bear in mind that this parameter must be used in conjunction with the parameter AllClassNext=Off. Default not configured.EXAMPLE: SelfNext=3AllClassesNext=Off

7 Mobile configuration optionsPage 96CELLX 16.27.7 Setting autodialWhen the following configuration is set, the gateway calls a defined list of phone numbersautomatically. Save the script in a text file with the extension *.ad.The autodial process starts automatically when the script file has been copied to /boot or /data. The file extension is renamed *.ax and is deleted when process has ended. A log file*.al is generated in the course of the process. The file contains whether the call was success-ful, the number called, the call duration for successful calls, and the cause value for failedcalls. To abort the process, simply delete the *.ax file.The following settings are possible:OPTION CALLDURATION: Enter an interval in seconds to define the length of the call.OPTION CALLRETRIES: Enter the number of call attempts for each number.OPTION CONFIGURATION: Refers to the number of the = configuration.OPTION NOALARM: Set this option to suppress sending alarms when connected to avGATE.D<sec>: Enter a value to define the duration for calls to this number.P<sec>: Enter a value to define the pause between calls.7.8 Disconnecting calls after ringWhen the following parameter is configured, the call will be disconnected once the numberof configured seconds have passed after the mobile network has sent the first ring:AWSTime=<sec>7.9 Checking ports/mobile channelsMonitoring ASR for mobile portsASR monitoring of the last 40 calls occurs for all mobile ports. If the ASR (ASR2) is lower than30 percent, an alarm is generated at the corresponding port and the port is blocked. The portis then restarted and a corresponding entry appears in the protocol.log file (ASR). The port isthen unblocked.The following entry in the pabx.cfg causes the mobile port to block automatically when thiserror occurs three times in a row:ASRBlock=OnWhen ASRBlock=Off is used, the port will be restarted and will remain open.The following parameter in the pabx.cfg file allows you to change the default value (30%for 40 calls): GSM=ASR[<percent>,<number of calls>] (for iGATE GSM)Example 7.12 Setting autodialOPTION CALLDURATION 155-170OPTION CALLRETRIES 2 OPTION CONFIGURATION 1OPTION NOALARM 017222921 D10 P30017222922 D10 P30017222923 D10 P30017222924 D10 P30

7 Mobile configuration optionsPage 97CELLX 16.2UMTS=ASR[<percent>,<number of calls>] (for iGATE UMTS)7.10 Defining special characters for voice callsIn cases in which the called number includes special characters (for example * or #), it may benecessary to define the call type used in the mobile network (command or voice call). Calls toGSM or CDMA that begin with * or #, are sent as command calls by default. For voice callsbeginning with * or #, you must define the call type voice in the mapping entry with a > sign.The routing entry will look like this:MapAll<num>=<LAIN>><num>Example 7.13 Monitoring ASR for mobile ports (iGATE GSM)GSM=ASR[20,35]Example 7.14 Monitoring ASR for mobile ports (iGATE UMTS)UMTS=ASR[20,35]Example 7.15 Defining special characters for voice callsMapAll222=11111>*222

8 Signaling and routing featuresPage 100CELLX 16.2corresponding mobile carriers (LAIN 26212 and 26213). All other national long distance andlocal calls are routed through an alternative carrier (01019). All calls from the PSTN to the PBXare put through transparently.8.1.2 Alternative routing settingsAlternative routing refers to the ability to establish connections using a different (alternative)network in case of provider failure (for example all mobile controllers are in use). Alternativerouting ensures uninterrupted operation of the attached PBX. In such cases, connections areoften made via the public network using the Redirect command.MapAll<num>=<port><num>Redirect3<port><num>=<placeholder>MapAll<placeholder>=<alt port><num>Example 8.1 Carrier selection routing entriesMapAll001=40iG1:001MapAll0044=40iG2:0044...MapAll01555=2621201555MapAll01556=2621301556...MapAll01=90101901MapAll02=90101902...MapAll09=90101909MapAll1=9010191MapAll2=9010192...MapAll9=9010199Restrict9=10Be sure to enter phone numbers in the routing file in ascending order.iiExample 8.2 Alternative routing settingsMapAll01555=2621201555Redirect32621201555=AMapAllA=901555

8 Signaling and routing featuresPage 101CELLX 16.28.1.3 Charge modelsCELLXs can either generate charge information or transmit received charges from the publicor corporate networks to the attached PBX. Charge simulation is achieved using variables,which ensure a great degree of flexibility for the implementation of many different chargemodels including:Charge units per time unitFlat rate (initial charge without time interval)Initial charge plus time intervalInitial charge plus time interval after delayTime interval and/or flat rate plus received chargesReceived charges only or no charge informationInitial toll-free period with retroactive charge generation afterwardsPrice-per-minute (with whole second accuracy)In this chapter, unit means that charge information is transmitted as a whole-numbered val-ue, and currency means that the charge information is sent as a currency amount (for exam-ple EUR 3.45). The charge impulse generation options can be set for each mapping by addingcharge-specific arguments to the MapAll commands as shown below. The use of each vari-able is explained in Table 8.1.MapAllsrc=dst mode time start/wait.Any external charges can be added to the generated charges by adding 128 to the start value.(The value range for the initial unit level is still set from 0 to 127). The maximum supportednumber of units per connection is 32767 units.Additional adjustments may be made to allow for the implementation of new charge models.When charge information is sent as Currency, values can be expressed in thousandthsfor greater precision in charge calculation.For the internal Layer 3 protocols, charges can be specified to the third decimal place(thousandth) using the /Value option (Example: /Value:1.056). In this fashion, chargescan be generated for units of currency requiring accuracy to the third decimal place orTable 8.1 Charge variables Variable Purposetime Determines the length of each time interval (how long each unit lasts). The value is entered in seconds and hundredths or thousandths of a second (the maximum value accepted is 655.35 seconds, 65.535 if thousandths are entered). If time is set to zero or not present no charges are generated, external charge information is passed through if received.start Optional. Sets the initial unit level. Enter a value between 0 and 127 whole units. If you want to use a flat rate, set the desired number of units here and set the wait to 255 to turn off the time interval.wait Optional. Determines the delay after which charge generation begins. Once this time has elapsed, charge impulses are sent in the interval de-termined with time. Enter a value between 0 and 254 seconds. 255 de-activates the charge pulse. In this case, the time variable is ignored.

$8 Signaling and routing featuresPage 102CELLX 16.2for fractions such as tenths of a cent. This allows for greater flexibility in thetransmission of charges to terminal devices. In order to make use of this option,connected devices must support “AOC-D Currency”. In the current version, this optionis only available for the DSS1 protocol.A multiplication factor can be specified for received or generated charges.During the charge generation process, each charge unit is multiplied by a preset factor.This factor appears in the mapping entry after the time and start/wait variables(MapAllsrc=dst mode time start/wait*factor).Each unit, for example, can be converted to 12 cents. The following example illustratesthe use of this feature.In this example, all received charge units are multiplied by 12 and passed on. If AOC-Currencyis set on the internal port, each unit appears as 12 cents. The multiplication factor is also usedto implement two new charge models:If the factor value exceeds 128, this marks the use of an initial toll-free phase followedby retroactive charge generation.If the multiplication factor is set to 255, a “minute price” is used in place of the timevariable.8.2 Online traffic monitorThe Online Traffic Monitor allows you to collect and monitor statistics and call detail records(CDRs). The following functions are possible with this feature package:ASR calculationGeneration of CDRsGeneration of online CDRs using e-mail8.2.1 ASR calculation and resetting statistic values and countersWhen these functions are configured in the pabx.cfg file, the following statistic values arecalculated for the entire system at a defined time and are copied into a file in the followingorder:Day and time of entrySystem nameNumber of connected calls followed by the number of total calls in parenthesesNumber of minutes termintatedASR1: ratio of total calls to connected calls disconnected by the A partyASR(ext): external ASR for the traffic sourceASR(int): internal ASR for the CELLXACD: average call durationThe following example shows how the statistics appear in the file into which they are copied.Example 8.3 Charge model...MapAll1=91 1 128/255*12...Example 8.4 Statistics file26.10.04-00:00:00,iGATE810000: Calls: 19351 (29716) - Minutes: 46647 - ASR1: 65.12% - ASR(ext): 65.12% - ASR(int): 65.30% - ACD: 144.63s$

8 Signaling and routing featuresPage 103CELLX 16.2Set the time using the following syntax: <hh:mm>. If ?? appears instead of a specified hour(for example ??:mm), the ASR is written into the asr.log file once every hour. You can set <day> to apply for days of the week or for one specific day of the month as fol-lows:Use a bitmask to set the weekdays on which the configuration applies here. The daymap ap-pears in the following order: HoSaFrThWeTuMoSu. For example, enter 00000001 if the con-figuration is to apply every Sunday. To set the configuration to apply on one specific day every month, enter the day of the monthfollowed by a full stop. For example, enter 15. if the configuration is to apply on the 15th ofevery month.If the configuration is to apply every day, do not set <day>.8.2.1.1 Saving and sending statisticsThe statistics are copied into a specified file. This information can also be sent to an e-mail orSMS recipient. The following syntax must be used: StatisticTime=/data/asr.log <hh:mm> <day>StatisticTime=/data/asr.log <hh:mm> <day> @<email address> StatisticTime=/data/asr.log <hh:mm> <day> @SMS<mobile number>In the following example, the system’s statistic values are saved every Wednesday into the fileasr.log and sent to an e-mail account.In the following example, the system’s statistic values are saved at midnight on the first ofevery month into the file asr.log and sent to an SMS recipient.Do not configure both StatisticTimeReset and StatisticTime or StatisticTimeReset and Statis-ticCounter together.iiExample 8.5 Saving and sending statistics 1StatisticTime=/data/asr.log 00:00 00001000 @info@teles.deExample 8.6 Saving and sending statistics 2StatisticTime=/data/asr.log 00:00 01. @SMS01234567890Do not configure both StatisticTimeReset and StatisticTime together.ii

8 Signaling and routing featuresPage 104CELLX 16.28.2.1.2 Saving statisticsThe statistics are copied into a specified file and the counters (A-F) are reset. The followingsyntax must be used: StatisticTimeReset=/data/asr.log <hh:mm> <day> In the following example, statistics will be saved every hour on the hour of every day and thestatistic counters will be reset to 0.In the following example, the system’s statistic values are saved at noon on the 15th of everymonth into the file asr.log.8.2.1.3 Resetting statistic countersThe following setting in the pabx.cfg resets the statistic counters and unblocks the controllergroup. The following syntax must be used: ResetCounter=<port> <hh:mm> <day> orResetCounter=<LAIN> <hh:mm> <day> Up to five entries for as many groups and/or times are possible. Bear in mind that StatisticTim-eReset must be inactive to avoid repetition. The mapping to a LAIN requires that in thepabx.cfg file, the CHADDR parameter is added to the Subscriber line, to change the con-troller definition to the SIM card’s LAIN.In the following example the counters will reset for LAIN group 26211 every day at midnight,for the group 26212 only once on the first day of the month, and for 26213 each Saturdayat 8:00pm.Example 8.7 Saving statistics 1StatisticTimeReset=/data/asr.log ??:00Example 8.8 Saving statistics 2StatisticTimeReset=/data/asr.log 12:00 15.Do not configure both StatisticTimeReset and StatisticTime or StatisticTimeReset and StatisticCounter together.iiExample 8.9 Resetting statistic countersResetCounter = 26211 00:00 11111111ResetCounter = 26212 00:00 01.ResetCounter = 26213 20:00 01000000

8 Signaling and routing featuresPage 105CELLX 16.28.2.2 Generating and retrieving CDRsWith the Log and failedlog commands, you save CDRs and unconnected calls in the CELLX. For these parameters (Log and failedlog), a folder and file name must always be specifiedafter the equal sign. The function is not active (no data is recorded) until a file name is spec-ified.The service indicator listed in the call log and missed calls list describes the type of connectionas a four digit hexadecimal number. The coding is conducted according to the 1TR6 standard.A few frequently used values are listed below.Do not configure both StatisticTimeReset and StatisticCounter together.iiExample 8.10 Generating and retrieving CDRsLog=/data/cdr.log failedlog=/data/failed.logWith recording of files, system maintenance increases. You have to be sure to download or delete files and ensure that there is enough disk space left on the hard drive.iiTable 8.2 Service indicator listService indicator Description0101 ISDN-telephony 3.1 kHz0102 analog telephony0103 ISDN-telephony 7 kHz0200 Fax group 20202 Fax group 30203 Data via modem0400 Telefax group 40500 SMS or BTX (64 kbps)0700 Data transfer 64 kbps1001 Video telephone – audio 3.1 kHz1002 Video telephone – audio 7 kHz1003 Video telephone – video

8 Signaling and routing featuresPage 106CELLX 16.2For detailed information on how to automatically divide the files (for example on a daily basis),please refer to the Chapter 5.2.1.2 Log files.8.2.2.1 Call logThe following entry in the pabx.cfg configuration file activates the capability to generateCDRs in the CELLX:Log=/data/cdr.logThe cdr.log file is stored in the data directory. New entries are always added to the end of thefile. The file is open only during editing. Each line represents an outgoing call with the following information separated by commas:Table 8.3 Call log entries Column Description0Version1Start time (format DD.MM.YY-hh.mm.ss)2End time (format DD.MM.YY-hh.mm.ss)3Source. The following format applies: [node number:automatically set internal channel number]4Destination. The following format applies: [node number:automatically set in-ternal channel number]5IMSI6IP logging signaling: RTP7Audio codec used8Frame size9Service indicator (please see Chapter 8.2.2 Generating and retrieving CDRs)10 Call duration11 Cause values12 Charge from the public line (in units)13 Charge generated from the system (in units)14 Cell ID15 RSSI

8 Signaling and routing featuresPage 107CELLX 16.2Sample log fileThe example below shows a sample log file.Differentiating between ports in the same trunk groupTo differentiate between ports with the same number in the CDRs, a specific node numbermust be defined. You can expand the subscriber configuration line with the keywordNODE[<num>] for this purpose. <num> can be a string of between 1 and 15 characters:Subscriber<xx>=... NODE[<num>]In the below formula, <num> consists of a four-digit number that is included in the CDR.Example 8.11 Sample log fileV1,25.11.09-10:16:20,25.11.09-10:16:27,[0000:01]9,[0006:01]111,123456789123451,,,,0102,7,1f,0,,3663,10V1,25.11.09-10:35:16,25.11.09-10:35:26,[0000:01]9,[0004:01]111,123456789123452,,,,0102,10,1f,0,3,38922,14V1,25.11.09-10:38:30,25.11.09-10:38:41,[0000:01]9,[0004:01]111,123456789123453,,,,0102,11,90,0,3,38922,14Example 8.12 Differentiating between ports in the same trunk group (CDR entry)V1,25.11.09-10:16:20,25.11.09-10:16:27,[0000:01]9,[0006:01]111,123456789123451,,,,0102,7,1f,0,,3663,10

8 Signaling and routing featuresPage 108CELLX 16.2The following example shows the pabx.cfg configuration file changed according to the for-mula.Differentiating between SIM cardsThe CDR can contain the IMSI (International Mobile Subscriber Identity), which identifies eachSIM card used.Example 8.13 Differentiating between ports in the same trunk group (pabx.cfg entry)...Subscriber00=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0001]Subscriber01=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0002]Subscriber02=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0003]Subscriber03=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0004]Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0005]Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0006]Subscriber06=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0007]Subscriber07=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0008]Subscriber08=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0009]Subscriber09=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0010]Subscriber10=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0011]Subscriber11=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0012]Subscriber12=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0013]Subscriber13=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0014]Subscriber14=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0015]Subscriber15=TRANSPARENT ROUTER GSM[0000,00000,<SMSC>,1,1,1,SIM24] CHADDR ALARM NEXT NODE[0016]...Example 8.14 Differentiating between SIM cards (CDR entry)V1,25.11.09-10:35:16,25.11.09-10:35:26,[0000:01]9,[0004:01]111,123456789123451,,,,0102,10,1f,0,3,38922,14

8 Signaling and routing featuresPage 110CELLX 16.2The following entry shows the route.cfg configuration file changed according to the for-mula.The following CDR entry includes IP addresses for signaling and voice data, audio codec andframe size.CDRs for callback and two stage callsIn the case of CDR entries for Two stage dialing/Callback calls, the beginning and endingtimes for the first call leg is always used as the call time. The call time in seconds appears firstfor the first leg, followed by a slash and the connection time for the second leg.Specific cause valuesThe CELLX will generate cause values that represent an event, such as exceeding a definedlimit.Example 8.16 Activating peer data for VoIP calls (route.cfg entry)[Voip:DF]VoipDirection=IOVoipPeerAddress=192.168.0.2VoipIpMask=0xffffffffVoipCompression=g729 t38VoipMaxChan=30VoipSilenceSuppression=Yes VoipSignalling=0VoipTxM=4VoipIPLogging=YesExample 8.17 Activating peer data for VoIP calls (CDR entry)V1,24.11.09-16:52:20,24.11.09-16:52:22,[0008:01]401419,[0006:01]IN777,123456789123451,172.20.25.103:172.20.25.103,G711a,20,0101,2,10,0,,34193,11Example 8.18 CDR entry for callback and two stage callsV1,24.11.09-17:15:29,24.11.09-17:15:57,[0002:01]CB,[0008:01]DLA,,172.20.25.103:172.20.25.103,G711a,20,0102,28/3,90,0,,,Table 8.4 Specific cause valuesCause value Description0a One of the following limits has been reached: Unit limit defined in the port’s subscriber line0b Maximum call duration assigned via vGATE has been reached.0c Maximum call duration based on mapping entry settings has been reached.

8 Signaling and routing featuresPage 111CELLX 16.28.2.2.2 Missed calls listAll incoming calls that are not connected can be recorded in a list to facilitate return calls.Recording is activated using the failedlog=<name> entry in the pabx.cfg. Specify a filename, for example failedlog=failed.log. Once this setting is made, recording begins at once.Each line represents an unaccepted incoming call with the following information separatedby commas.0d Maximum number of minutes per SIM assignment via vGATE has been reached.10, 1f Normal call termination (disconnected by calling party).To avoid sending these values as the reason for call teardown, translate the cause values to standard values Chapter 8.14 Changing cause values.Table 8.4 Specific cause valuesCause value DescriptioniiTable 8.5 Failed log entries Column Description0Version1Start time (format DD.MM.YY-hh.mm.ss)2Source. The following format applies: [node number:automatically set internal channel number]3Destination. The following format applies: [node number:automatically set inter-nal channel number]4IMSI5IP logging signaling: RTP6Audio codec used7Frame size8Service indicator (please see Chapter 8.2.2 Generating and retrieving CDRs)9Cause values10 Call duration (if the call does not result in an Alerting, the entry will be -1)11 Number of call attempts12 Cell ID13 RSSI

8 Signaling and routing featuresPage 112CELLX 16.2The reason the connection could not be established is specified using DSS1 codes:91 – (user busy)ff – call not answered (disconnected by calling party)When callback with DTMF is configured and no connection is established to the B subscriber,an entry recording the A subscriber’s connection time is generated in the failed.log file.The CDR contains the IP addresses for signaling and voice data. The first IP address is the sig-naling address and the second one is the RTP address.The IMSI is written behind the IP ad-dresses if the keyword IMSI is defined in the pabx.cfg.In the case of missed-call entries for Two stage dialing/Callback calls, dur is the connectiontime for the first leg.8.2.2.3 Sending CDRs via e-mailWith an appropriate configuration, you can send corresponding CDRs of outgoing and in-coming calls as e-mail. Bear in mind that the mail server must be configured in the [Mail] sec-tion of the pabx.cfg, as described in Chapter 5.2.2 SMTP-client configuration. The sender isgiven as cdr and the system’s name appears in the subject box. The text box contains the CDRExample 8.19 Failed.log fileV1,24.11.09-16:13:08,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,9V1,24.11.09-16:33:34,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,12V1,24.11.09-16:35:19,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:35:59,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:37:29,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,92,-1,1,34193,11V1,24.11.09-16:39:17,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,ff,7,1,34193,11Example 8.20 Failed.log entry 1V1,24.11.09-16:39:17,[0006:01]IN,[0008:01]GSM,123456789123456,,,,0101,ff,7,1,34193,11Example 8.21 Failed.log entry 2V1,24.11.09-16:52:20,24.11.09-16:52:22,[0008:01]401419,[0006:01]IN777,262032441017556,172.20.25.103:172.20.25.103,G711a,20,0101,2,10,0,,34193,11Example 8.22 Failed.log entry 3V1,25.11.09-14:11:10,[0002:01]CB,DLA,,,,,0102,11,14,1,,

8 Signaling and routing featuresPage 113CELLX 16.2information according to the format for the entry in Log=/data/cdr.log @<account> @<do-main>. A space must appear between cdr.log and @<account>; @<domain> is optional. Youcan also send CDR entries via e-mail to an e-mail recipient. Enter an @ sign to send each CDR entry as e-mail: Log=/data/cdr.log @<e-mail account>@<domain>If you enter a ! the entire cdr.log will be sent as an e-mail attachment:Log=/data/cdr.log !<e-mail account>@<domain>8.3 Ported number screeningPorted number screening is a very useful functionality to avoid high routing costs for numbersthat have been ported to another network operator.Number portabilty refers to the ability to transfer either an existing fixed-line or mobile tele-phone number to another network operator. This way telecommunications subscribers canchange operators without having to change their telephone numbers. Routing ported num-bers, however, can become very cost intensive due to differences in tariffs.With ported number screening, an external database is queried to find out if a number hasbeen ported. Either use the iMNP for querying the external database or query the databasedirectly. The iMNP is a proxy that remembers the database information for a defined periodof time and renews the query to the external database only after that period has passed. Sinceevery query to the external database costs money, the iMNP helps to reduce querying costs.The qery result is used in a routing to route the call via the right network operator. To implement ported number screening, make sure to meet the system requirements whichare:An active license for number portability.An iMNP server or another appropriate server.Also ensure to adjust your configuration:To connect to the number portability database, you must set the entries described inChapter 5.2.3 Number portability settings.Configure your route.cfg file to activate ported number screening:DTMFWaitDial=<sec>Set the time that the gateway waits for additional digits.MapAll<num>=|$<prefix><num><<<count>Enable digit collection (pipe symbol) and collect up to the number of digits that isspecified under count. Add the dollar sign to search the routing table again. Prefix thenumber with a freely chosen prefix to prepare it for sending to the database.MapAll<prefix>=|D@<num><<01Send the prefixed number to the database. Make sure that the prefix used here matchesthe above prefix.MapAllQN<query result>=<controller>Map the query result to the respective controller. The query result consists of the LAINand the number including the country code. Do not forget to also configure routingsfor numbers that haven’t been found in the database or that do not exist and alsoprovide a routing when the server does not respond in a defined period of time.In the following example, 14 digits are collected (11 digits plus $ph) and a maximum time of5 seconds is waited for each digit. Every incoming call with a leading digit of 0 results in aniMNP query. The SIM card’s LAIN is used instead of controller numbers. All numbers thatcome back from the iMNP with the LAIN for Carrier_1 (26211) are then routed through

8 Signaling and routing featuresPage 114CELLX 16.2Carrier_1’s SIM card. The same applies for Carrier_2 (26212), Carrier_3 (26213) and Carrier_4(26214). Numbers that the iMNP sends back as non-existing (00000) are rejected. Numbersthat may exist but are not found in the database (99999) are routed as they come in (normal).If the iMNP does not respond within two seconds (D@0), the call is routed as it comes in,whether it is ported or not.8.4 Digit collection (enblock/overlap receiving)This function makes it possible to collect up to 24 digits and transmit calls when a specificnumber of digits has been dialed. The entire call number is required for the call to be set upwith a mobile phone or the mobile gateway. Since most numbers have a uniform number ofdigits, the mobile gateway can collect digits when calls enter the gateway in overlap mode.Digit collection occurs through the following mapping command:MapAll<direct>=|<num><<<digits>The | (pipe) signifies that the following digits will be collected before they are transmitted, and<digits> is the total number of the port digits and the digits of the called party number. Thisfigure can range between 00 and 24 and must be entered in double digits. The parameterDTMFWaitDial defines the number of seconds the system waits between the individual digits(default 5). Please bear in mind that you can configure a maximum of 11 digits in the first partof the command and 19 (including a special character, for example #) in the second. The callwill be forwarded as soon as the specified number of digits has been dialed or a time-out limithas been reached.Example 8.23 Ported number screeningDTMFWaitDial=5MapAll0=|$ph0<<14MapAllph=|D@0<<01MapAllQN26211=26211MapAllQN26212=26212MapAllQN26213=26213MapAllQN26214=26214MapAllQN00000=&81MapAllQN99999=$normalMapAllD@0=$normal1; not in Database ;Carrier_1MapAllnormal0151=262110151MapAllnormal0160=262110160MapAllnormal0170=262110170MapAllnormal0171=262110171MapAllnormal0175=262110175;Carrier_2MapAllnormal0152=262120152MapAllnormal0162=262120162MapAllnormal0172=262120172MapAllnormal0173=262120173MapAllnormal0174=262120174;Carrier_3MapAllnormal0155=262130155MapAllnormal0163=262130163MapAllnormal0177=262130177MapAllnormal0178=262130178;Carrier_4MapAllnormal0159=262140159MapAllnormal0176=262140176MapAllnormal0179=262140179

8 Signaling and routing featuresPage 118CELLX 16.2Use the following configuration to define the various routing methods.InsertCLIR=On activates this mode. 01 is the service indicator for telephony (analog and ISDN)and is used to differentiate these calls from remote administration calls. Restrict9=OK 01means that all telephony calls without a calling number are put through. Restrict|9=OK 01means that all CLIR telephony calls are put through. Restrict90=FAIL 01 means that all CLIPtelephony calls are rejected with No Channel Available as rejection cause when they aremapped to MapInFAIL=&aa. 8.6.2 Routing calls without CLIRUse this function to bypass CLIR for calls through the defined mobile port. The following con-figuration in pabx.cfg activates this function.8.6.2.1 Setting CLIRSetting a hash (#) in front of a call number makes it possible to suppress the presentation ofthe origination number of calls regardless of how the call comes into the system.The following syntax is used: MapAll<num>=#<port><num>.The following example shows an appropriate configuration. With this entry, all calls begin-ning with 00491555 are sent to the port with the address 22 and the presentation of thenumber is restricted.Example 8.30 Routing CLIP and CLIR calls...InsertCLIR=On...Restrict9=OK 01Restrict|9=OK 01Restrict90=FAIL 01...MapInOK00491555=2200491555MapInFAIL=&aa...Example 8.31 Routing calls without CLIRSubscriber<xx>=...GSM[...,!CLIR]...When this function is configured, the SIM’s telephone number (and not originating telephone) is always transmitted to the B subscriber.iiExample 8.32 Setting CLIRMapAll00491555=#2200491555

8 Signaling and routing featuresPage 119CELLX 16.28.6.2.2 Setting CLIPSetting an exclamation point (!) in front of a call number makes it possible to force the pre-sentation of the origination number of calls regardless of how the call comes into the system.The following syntax is used: MapAll<num>=!<port><num>The following example shows an appropriate configuration. With this entry, all calls begin-ning with 004930 are sent to the port with the address 9 and the presentation of the origi-nation number is allowed.8.7 Conversion of call numbersThe conversion of call numbers makes it possible, for example, to implement number porta-bility or to redirect calls when the user can be reached at another number. In the followingmapping command, the call number 015550123456 is changed to 015559876543 and sentto the mobile channel (MapAll...=20..)The following example presents an alternative, in which the routing file is searched throughagain after conversion of the call number to determine the route for the prefix 01555. Pleasebear in mind that you can configure a maximum of 1499 mapping entries with no more than11 digits in the first part of the command and 19 in the second.8.8 Overwriting OADIn some cases where the OAD is not transmitted or shall for other reasons be overwritten, thefollowing parameter can be used to send another OAD:Restrict<port>=<OAD to be sent> 15 orRestrict<port><original OAD>=<OAD to be sent> 15For PRI ports only: extend this parameter by a text in quotation marks to transmit a displayinfo element in a PRI or SIP call. If supported by the receiving telephone, the content of thedisplay field is displayed in addition or instead of the OAD.Restrict<port>=<OAD to be sent> 15 “display field“ orRestrict<port><original OAD>=<OAD to be sent> 15 “display field“Example 8.33 Setting CLIPMapAll004930=!9004930Example 8.34 Conversion of call numbers 1MapAll015550123456=20015559876543Example 8.35 Conversion of call numbers 2MapAll015550123451=$ReceptionMapAll015550123452=$ReceptionMapAll015550123453=$ReceptionMapAllReception=015559876543

8 Signaling and routing featuresPage 120CELLX 16.2In the following example, the text “Teles Marketing” and / or the OAD 456 are displayed tothe called person for calls that have been received via port 10.8.9 Setting number type in OAD/DADIn some cases it may be necessary to set a specific number type for the OAD or DAD. Thereare different methods for the various interfaces. The following number types can be set. OADUse the following entry to set a specific number type in the OAD:Restrict<port><num>=<type> 15For the national and international types, remove the 0(s) at the beginning of the number:Restrict<port>0=n 15Restrict<port>00=i 15In the following example, the bit is set in the caller’s origination number for a call via BRI con-troller 01.You can set a u (unknown type of number) in the Restrict entry to change transmission of thenational/international bit to 0 or 00 at the beginning of the OAD. As in a mapping entry, thenational/international bit will always appear left of the equal sign as 0 or 00.Restrict<port>0=u0 15Restrict<port>00=u00 15Example 8.36 Overwriting OADRestrict10=456 15 “TELES Marketing“Table 8.6 Number types Ty p e Descriptionu UnknownsSubscriber numbern National numberiInternational numberExample 8.37 Setting number type in OAD 1Restrict90=n 15Restrict900=i 15

8 Signaling and routing featuresPage 123CELLX 16.2In the following Restrict example, the screening indicator is specified as network provided,and the number type is international.Please bear in mind that this entry will not work if you set a minus sign (-) behind Voi-pOad=<num>.8.11 Setting a default OADUse the Restrict command to set a default origination number (*<oad> 15) when the OAD isrestricted (<num>):Restrict<port><oad>=*<num> 15 In the following example, 12345 replaces the original OAD. When the destination numberbegins with 030, the call is sent through controller 10.Use the entry Restrict<port><oad>=<num> 15 if digits at the beginning of the OAD are theonly ones to be restricted. In the following example, the digits 004930 are replaced with 030 followed by the remainingdigits. The destination number begins with 030 and is sent through port 10.8.12 Setting or removing sending complete byte in setupIn some cases the ISDN or H323 peer system may require this byte for routing, or the bytemay disrupt signaling. Setting sending completeThe following entry ensures that the Setup includes a Sending Complete:MapAll<direct>=)<num>The ) causes inclusion of Sending Complete in the ISDN Setup or in the H323 Setup.Example 8.45 Setting the screening indicator 3Restrict10=ip 15Example 8.46 Setting a default OAD 1Restrict9=*12345 15MapAll030=10030Example 8.47 Setting a default OAD 2Restrict9004930=030 15MapAll030=10030

8 Signaling and routing featuresPage 126CELLX 16.28.14 Changing cause valuesIt is possible to group cause values together into a single defined cause value so that rejectedcalls can be handled in a specified manner by the switch sending the call to the CELLX. Thefollowing cause value groups can be defined in the pabx.cfg:Group 0 cause valuesAll connections that are rejected with a group 0 cause value (0x80-0x8f) can be mapped to asingle cause value by entering TranslateG0Cause=<cau>, whereby <cau> represents acause value in hexadecimal form.Group 1 cause valuesAll connections that are rejected with a group 1 cause value (0x90-0x9f) can be mapped to asingle cause value by entering TranslateG1Cause=<cau>, whereby <cau> represents acause value in hexadecimal form.Group 2 cause valuesAll connections that are rejected with a group 2 cause value (0xa0-0xaf) can be mapped to asingle cause value by entering TranslateG2Cause=<cau>, whereby <cau> represents acause value in hexadecimal form.Group 3 cause valuesAll connections that are rejected with a group 3 cause value (0xb0-0xbf) can be mapped to asingle cause value by entering TranslateG3Cause=<cau>, whereby <cau> represents acause value in hexadecimal form.Translating individual cause valuesThe following parameter allows you to translate any of these cause values to any other one:Translate<cause>=<cause>. The values entered must be in hexadecimal notation between00 and 7f.Translating SIP causes to ISDN and vice versaYou can define a specific translation from SIP responses (4xx - 6xx) to ISDN cause values andvice versa. If nothing is set, the translation occurs as described in draft-kotar-sipping-dss1-sip-iw-01.txt.Use the following parameter to translate a cause from ISDN to a specific SIP response: SipCause<ISDN cause>=<SIP Response>Repeat the entry to initiate an additional translation.Use the following parameter to translate a cause from SIP to ISDN:SipEvent<SIP Response>=<ISDN Cause>The following range of values applies:400<= <SIP Cause> <=699 (defined in RFC 3261)0<= <ISDN Cause> <=127 (DSS1 decimal cause number)8.15 Call forkingThe call forking functionality is mostly used to send inbound calls to your PBX extension andmobile phone simultaneously. Calls can be answered from either the extension or the mobilephone.

8 Signaling and routing featuresPage 127CELLX 16.2To activate this feature, you need to add two parameters to the route.cfg: GlobalIn andGlobalOut.Before adding call forking functionality to your route.cfg, check whether the necessarymapping of a destination number to a port plus new destination number exists:MapAll<destinationNumber>=<port><newDestinationNumber>For routing to a VoIP port, the following syntax is used:MapAll<destinationNumber>=<voipPort><voipProfile>:<newDestinationNumber>The parameters destination number and new destination number do not need to be identical.To activate call forking, add the following entries behind the mappings:Assign the port plus new destination number to the parameter GlobalIn<int>. You can de-fine up to 32 different GlobalIn configurations.GlobalIn<int>=<port><newDestinationNumber> where int >= 1For VoIP, the following syntax is used:GlobalIn<int>=<voipPort><voipProfile>:<newDestinationNumber> where int >= 1Assign the numbers which you want to call simultaneously to the GlobalOut<int> parame-ter. The integer value is used to map GlobalIn to GlobalOut. You can define up to 32 dif-ferent GlobalOut configurations.GlobalOut<int>=<destinationNumber1> <destinationNumber2> where int >= 1Be aware that for both destination numbers the MapAll parameter needs to be set. This mustbe done before the forking.In this example two mappings exist: calls to the destination number 543211234 are mappedto the port 10 and the new destination number 543211234. Calls to the destination number01721234554 are mapped to the port 20 and the new destination number 01721234554.Before the call is sent out, the system checks the route.cfg for a matching GlobalIn pa-rameter. A match is found for calls to 10543211234 and calls to this number are sent to543211234 and 01721234554 simultaneously.Example 8.53 Call forkingMapAll543211234=10543211234MapAll01721234554=2001721234554...GlobalIn1=10543211234GlobalOut1=543211234 01721234554

9 Additional VoIP parametersPage 129CELLX 16.2You can enter the following additional parameters in the route.cfg to adjust the configu-ration for improved communication with the VoIP peer.9.1 Signaling parameters Table 9.1 Customized parameters: protocol-independent VoIP signaling Protocol-Independent VoIP Signaling ParametersVoipComprMaster=<mode>This parameter defines which side the first matching codec comes from:Yes: Default. Priority is determined by the order of the system’s parameter list.No: Priority is determined by the peer.VoipConnectOnCallProc=<mode>Enter Yes (default No) to change an H.323 Call Proceeding/Call Progress and Alert, or a SIP 180 or 183, into an H.323 Connect or SIP 200 message. This parameter can be used if an announce-ment that plays before the Connect requires a Connect on the other side to put through the call.VoipDad=<num>The digits/numbers defined here will appear in front of the original DAD as described for the pa-rameter VoipOad below. If the parameter is to be valid in only one direction, you must also set the parameter VoipDadIn or VoipDadOut .VoipDadIn=<string>Specifies that the parameter VoipDad is for incoming calls only. If this parameter is not set (de-fault), VoipDad will apply for both directions.VoipDadOut=<string>Specifies that the parameter VoipDad is for outgoing calls only. If this parameter is not set (de-fault), VoipDad will apply for both directions.VoipDataBypassPayloadType=<num>Defines the payload type for the RTP packets when the call is sent as a data call. Default 96.VoIPEarlyT38=<mode>Enter yes to enable T38 before the call has been connected. Enter no to enable T38 after the call has been connected. Default yes.VoIPEarlyVP=<mode>Activates the vocoder chip caused by an incoming SIP 180 or 183 without sdp. Fax tones coming from ISDN are already recognized before the connect and can thus prepare or even allow a switch to T38. Default no.VoipG72616PayloadType=<num>Changes the SIP payload type for G.726 16 b/s. Default is 35. A common alternative is one of the dynamic payload types from 96 to 127.VoipG72624PayloadType=<num>Changes the SIP payload type for G.726 24 b/s. Default is 36. A common alternative is one of the dynamic payload types from 96 to 127.VoipG72632PayloadType=<num>Changes the SIP payload type for G.726 32 b/s. Default is 2. A common alternative is one of the dy-namic payload types from 96 to 127.VoipG72640PayloadType=<num>Changes the SIP payload type for G.726 40 b/s. Default is 38. A common alternative is one of the dy-namic payload types from 96 to 127.

9 Additional VoIP parametersPage 130CELLX 16.2VoipHideOadByRemove=<mode>If Yes is configured and call setup is to VoIP, the OAD will be removed from signaling if presenta-tion restricted or user-provided, not screened is set in the calling party’s presentation or screening indicator. No (default) means no change will occur.NOTE: If the SIP protocol is used, Anonymous will always appear as the account in the From field. Transmission of the OAD can occur in the P-asserted header.VoipIgnoreDADType=<mode>Enter yes to change the DAD type to unknown, for example from international. The type is lost, for example the leading 00 bit is removed. Default no.Table 9.1 Customized parameters: protocol-independent VoIP signaling (continued)Protocol-Independent VoIP Signaling Parameters

$9 Additional VoIP parametersPage 131CELLX 16.2VoipOad=<num>In the following examples, the OAD is 5175551212.The digits/numbers defined here will be transmitted in front of the original OAD. In the following example, 001 will appear in front of the number 5175551212.EXAMPLE: VoipOad=001To transmit only OADs consisting of more digits than those defined, enter a !, followed by the number of digits, at the end of the entry. If the OAD has more digits, it will be transmitted un-changed. If it has the same number or fewer digits, only the string in front of the ! will be added in front of the OAD. In the following example, the digits 0015175551212 will appear::EXAMPLE: VoipOad=001!10If a minus (-) is entered, the original OAD will not appear. In the following example, no number will be transmitted.EXAMPLE: VoipOad=-If integers are entered before the minus sign, only the digits entered in front of the minus sign will be displayed. In the following example, 789 will appear.EXAMPLE: VoipOad=789-If an integer is entered after the minus sign, this number of digits will be removed from the be-ginning of the OAD. In the following example, 517 will be removed from the OAD:EXAMPLE: VoipOad=-3If -\ is entered followed by the first part of an OAD, that part will be removed. If the string does not match, the OAD will be transmitted unchanged. In the following example, only 1212 will be transmitted.EXAMPLE: VoipOad=-\517555To modify the original OAD, enter random<x>, whereby x represents a number of random digits between 1 and 10 that will appear in the OAD. In the following example, 001 plus 2 random digits plus the original OAD will appear.EXAMPLE: VoipOad=001random2If --\ is entered followed by a part of an OAD (not necessarily the first part), the OAD will not be transmitted at all. If the string does not match, the OAD will be transmitted unchanged. In the following example, the OAD is not transmitted.EXAMPLE: VoipOad=--\555If -<num>-\ is entered followed by a part of an OAD (not necessarily the first part), the entered number of digits is cut from the OAD and the remaining OAD is searched for the entered part. If it is found, the OAD will not be transmitted. If the string does not match, the remaining OAD will be transmitted. In the following example, the OAD is not transmitted.EXAMPLE: VoipOad=-3-\555In the following example, the remaining OAD 5551212 is transmitted.EXAMPLE: VoipOad=-3-\444Enter -\x\y\ to replace the digits x by the digits y. x must be at the beginning of the OAD. x and y can differ in length.In the following example, the digits 517 are replaced by the digits 00517.EXAMPLE: VoipOad=-517\00517\Enter -\?\y\ to replace any first digits with y. ? is used as a placeholder for one digit. ? and y can have different lengths.In the following example, the first three digits are replaced by 00517.EXAMPLE: VoipOad=-???\00517\Use a semicolon to concatenate several VoipOad commands. The commands are processed from left to right.In the following example, the first three digits are removed from the beginning of the OAD. In the remaining OAD, the first three digits are replaced by 444. The OAD 4441212 is transmitted.EXAMPLE: VoipOad=-3;-???\444\NOTE: If the parameter is to be valid in only one direction, you must also set the parameter VoipOadIn or VoipOadOut .VoipOadIn=<string>Specifies that the parameter VoipOad is for incoming calls only. If this parameter is not set (de-fault), VoipOad will apply for both directions.Table 9.1 Customized parameters: protocol-independent VoIP signaling (continued)Protocol-Independent VoIP Signaling Parameters$

9 Additional VoIP parametersPage 132CELLX 16.2VoipOadOut=<string>Specifies that the parameter VoipOad is for outgoing calls only. If this parameter is not set (de-fault), VoipOad will apply for both directions.VoipProgress=<int>For H.323: 0=progress indicator is not transmitted. 1 (default)=progress indicator is transmitted. 2=address complete message is transmitted. 3=call proceeding message type changed in alerting message type.For SIP: 0=183 response ignored and not sent. 1=183 response changed to a progress message with inband-info-available at the ISDN interface (default). 2=183 response changed to an address complete message at the ISDN interface. 3=183 response changed to an alerting at the ISDN in-terface.VoipSignalCLIR=<string>When the configured string appears at the beginning of the OAD and the parameter VoipHideOadByRemove is set, the OAD is removed from signaling, regardless of the presentation bits in the calling party field. If the parameter VoipHideOadByRemove is not set (default), the pre-sentation bits are set at presentation restricted (CLIR) if <string> is -. If the string matches the first digits of the OAD and it comes in with CLIP, the call will be sent to VoIP using CLIR. If the call comes in with CLIR, the string will be added to the beginning of the OAD and CLIR will be re-moved in the signaling. VoipSingleTcpSession=<mode>Enter Yes to send all outgoing VoIP connections in a single TCP session. Enter No (default) for an extra TCP session for each VoIP connection.VoipSuppressInbandInfoAvailableIndicatorInCallProceeding=<mode>Enter yes to send or receive the Progress Indicator in the Q.931 Call Proceeding message. Default no.VoipTrpPayloadType=<num>Defines the payload type for data calls when trp (transparent/clear mode) is used as codec in Voip-Compression=<list>. Default is 56. A common value is 102.Table 9.2 Customized parameters: H.323 signaling H.323 Signaling ParametersVoipCanOverlapSend=<mode>Enter off to deactivate overlap sending during setup (default on).VoipH245Transport=<int>This option determines the H.245 offer. 0 (default)=all signaling variants are offered; 1=FastStart only; 2=H.245 tunneling only; 3=extra session.VoipMapAddressType=<mode>For calls from PSTN to VoIP only. Enter yes to change the 00 at the beginning of a number to international and 0 to national.VoipMCinRLC= <mode>Enter Yes to cause the system to send the media channel capability in the reverse logical channel parameters as part of the H.245 negotiation (default No).VoipRejectIncomingNonMatchingFaststart=<mode>Setup will be rejected if the RTP codecs offered for incoming H.323 call setup with Faststart ele-ments do not match those configured in the parameter VoipCompression. Default No.VoipRestrictTCS=<mode>If Yes is entered, the response in the H.323 tunneling terminal capability set contains only the co-decs offered by the peer and not those configured in the system. Default No.Table 9.1 Customized parameters: protocol-independent VoIP signaling (continued)Protocol-Independent VoIP Signaling Parameters

9 Additional VoIP parametersPage 133CELLX 16.2VoipService=0x<service indicator>This parameter sets the ISDN bearer capability. For example, it can be used for calls coming from VoIP with the bearer capability data. You can define the service indicator as it is in the 1TR6 code:101 - ISDN 3,1kHz 102 - analog 103 - ISDN 7kHz201 - Fax 2 202 - Fax 3 203 - Fax 4 700 - DataNormally 101 is used. You can send another value to a switch that wants to handle VoIP calls dif-ferently from PSTN calls.EXAMPLE:VoipService=0x101VoipSetupAck=<int>1=setup acknowledge is transmitted; 0= setup acknowledge is not transmitted; 2 (default) =transmitted with H.323 information.Table 9.3 Customized parameters: SIP signaling SIP Signaling ParametersVoipAckWithSdp=<mode>Enter yes to send the SDP content in the SIP ack message. Default no.VoipAllow=<list>The allow header shows the supported methods and can be set here.EXAMPLE: VoipAllow=INVITE,BYEThe default setting includes the following:INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFERIt may be necessary to remove some of these entries for some peers.VoipAllowTlsAoc99=<yes/no>If the AOC99 information (charging information) is sent within a SIP-info-message and this pa-rameter is set to yes, the AOC information is evaluated. The default value is yes. VoipAngleBracketIsReserved=<yes/no>Enter yes to to replace < or > in the SIP uri by their ASCII encoding %3c or %3e. Is needed when a peer does not accept < or >. Default no.VoipContact=<account@domain>Used for the Contact field in Sip-Invite and Sip-Response messages.VoipContactParam=<string>Sets additional header parameters in the contact field.VoipDadSource=<int>SIP only: defines the field from which field the called party number coming from SIP is to be taken:0 = URL or URI in the Invite request that contains only digits, otherwise the To: field is used (de-fault)1 = To: field2 = Remote-Party-ID with party = called4 = URL or URI in the Invite request that can also contain letters8 = Diversion header (in case a redirect number is to be used as destination number)Table 9.2 Customized parameters: H.323 signaling (continued)H.323 Signaling Parameters

9 Additional VoIP parametersPage 134CELLX 16.2VoipDelayDisc=<mode>Yes (default) delays confirmation transmission during call teardown. That means the release tone is audible when the peer tears down the call.NOTE: For versions 13.0c or lower: To improve ASR, we recommend that you set this parameter to Yes if you use the parameter VoipMaxChan.VoipInfoSamOnly=<mode>This parameter determines the behavior in the case of overlap sending (VoipOverlap must also be set). Yes means that the contents of the SubsequentNumber field in info method will be attached to the URI’s available digits or to the invite message’s To field. No (default) means that the digit contents of the SubsequentNumber field will be used.VoipOadSource=<int>SIP only: defines the field from which field the calling party number coming from SIP is to be tak-en:0 = From: field (default)1 = Remote-Party-ID2 = P-Preferred-Identity4 = P-Asserted-Identity8= Display fieldNOTE: If 2 or 4 are entered, the number in the field must begin with tel:Going to SIP, the OAD is written in the following field:0 = From: field (default)1 = Remote-Party-ID (if VoipOwnAddress is not set)For the fields P-Preferred-Identity and P-Asserted-Identity, please check the corresponding param-eters. If the number is sent with CLIR to SIP, the From: field contains anonymous@anonymous.in-valid. If the number has to appear in the From: Field, the decimal value of the parameter must be increased by 8.VoipOverlap=<mode>SIP only. Enter yes to activate signaling with overlap sending, as per draft-zhang-sipping-overlap-01.txt. That means digit collection is no longer necessary in the routing when the digets come from ISDN with overlap sending. When this parameter is active, VoipPrack is automatically set to yes. Default is no.VoipOwnAddress=<account@domain>Used for the From field in Sip-Invite and Sip-Response messages. If only the domain is entered, the origination address (for example from ISDN) followed by an @ sign will automatically be set at the beginning.If the keyword IMSI appears in the parameter and the call is from GSM to VoIP, the SIM cards IMSI is transmitted in the FROM field:EXAMPLE: VoipOwnAddress=IMSI@CELLX01VoipOwnDisplay=<string>The entry is sent as Display Name in the From Field in SIP transmissions. The keyword MSN causes the calling telephone’s MSN to be transmitted as Display Name. The keyword DSP causes the ISDN display information element to be transmitted as Display Name. Default: no setting.Example: From: "John" <sip:493011111@teles.de>VoipP-Asserted-Identity=<string>Sets the P-Asserted-Identity field in the SIP invite message. The following settings are possible to-ward SIP:* The OAD coming from ISDN is transmitted.<string> The defined string is transmittedA combination of both is possible. Examples: 030* or tel:* or sip:user@carrier.deTable 9.3 Customized parameters: SIP signaling (continued)SIP Signaling Parameters

9 Additional VoIP parametersPage 144CELLX 16.29.7 DTMF parametersVoipV32Transport=<mode> 0=disabled (default), 2=bypass .VoipV34Transport=<mode> 0=disabled (default), 2= bypass.Table 9.10 Customized parameters: VoIP DTMF VoIP DTMF ParametersVoipComprDtmfInband=<list>This parameter always forced DTMF-tone inband transmission for the configured voice codes, re-gardless of what is configured for: VoipDtmfTransport=. The same codecs can be configured as for VoipCompression=<list>VoipDtmfFallback=<int>If VoipDtmfTransport=3 is set and the peer does not support DTMF transmission according to RFC 2833, the following settings apply:2 = automatic fallback to inband0 = automatic fallback to signaling messages (default) VoipDtmfTransport=<int> 0 (H323) = DTMF relayed with H.225 signaling information. 0 (SIP) = DTMF relayed with SIP INFO.1 = DTMF taken from audio stream and relayed to remote, meanwhile no rtp data is sent.2 (default) = DTMF and MF kept in audio stream and not relayed. 3 = DTMF taken from audio stream and relayed to remote as per RFC2833, meanwhile rtp data with silence is sent.4 = For SIP, SIP INFO messages will be converted to DTMF. For H.323, the H.245 user input will be converted to DTMF.6 (H.323 only) DTMF relayed with H245 user input.8 DTMF taken from audiostream to be further processed in the gateway.VoipIBSDetectDir=<int>Enter 1 and DTMF tones (and all other inband signaling) will be detected from the Ethernet side. Enter 0 for DTMF tones to be detected from the PCM side (default). DTMF tones from the Ether-net side are transmitted to the host as ISDN dialing information only if 1 is entered. In this case, set VoipDtmfTransport to 1 or 3. NOTE: If 1 is entered, fax detection is not supported.VoipMinDigitOnTime=<ms>Defines the minimum length of DTMF tones, to ensure DTMF tone detection. Default 0.VoipMinInterDigitTime=<ms>Sets a time interval for DTMF tone detection. Default 0.VoipRFC2833PayloadType=<num>This parameter changes the DTMF payload type. The default value is 96, a common value is 101.Table 9.9 Customized parameters: VoIP fax (continued)VoIP Fax/Modem Parameters

10 System maintenance and software update

10 System maintenance and software updatePage 146CELLX 16.210.1 Configuration errorsWhen typographical errors are made in the configuration files, an entry appears in the pro-tocol.log when the configuration is activated. This entry includes the line number and itscontents.10.2 Status and error messagesThe protocol.log file – assigned as the file for logging the protocol in the configuration file(ActionLog=file) – contains information on all activities within the system. In the example below, you can see that all activities are recorded beginning with the date andtime. If functions were activated by key combinations from terminal devices you can identifythese along with the service ID.Example 10.1 Status and error messages16.05.06-11:51:31,[990]Start STATUS - TELES.iGATE V11.7a (007f)16.05.06-12:10:57,[01A]ERR: Layer1 16.05.06-12:10:58,[000]ERR: OK 16.05.06-12:10:58,[010]ERR: OK 16.05.06-12:12:06,Remote Control from IP 192.168.1.216.05.06-12:12:06,Remote Control: OK 16.05.06-12:12:16,Activate Configuration System 16.05.06-12:16:26,Remote Control Terminated 16.05.06-14:00:00,Activate Configuration Night2 16.05.06-14:00:00,Time Switch Operation 16.05.06-18:00:00,Activate Configuration Night3 16.05.06-18:00:00,Time Switch Operation Table 10.1 Event log messages Message NMS DefinitionStatus Program[990] Start STATUS XTELES system software and sta-tus program have been started. System Start[999] System-Boot XSystem restarted by timer.[999] Remote Control: Reboot System restarted by remote ad-ministration command.Configuration ChangesActivate configuration <num> OKConfiguration <num> success-fully loaded. Initiator displayed in next line.Activate configuration <num> failed [<err>]Configuration <num> could not be loaded. Remote Control: Date & Time changedDate and/or time were changed via remote adminis-tration.

10 System maintenance and software updatePage 147CELLX 16.2Time Switch Operation The configuration change was made by the timer.Remote AdministrationRemote Control from <peer>, <RemoteCode>, <service>, 0Remote administration access from number or IP address.Remote Control: OK Successful remote administra-tion access.[993]Remote Control: wrong passwordX Remote administration access was denied because of a wrong password.[994]Remote Control: wrong numberXRemote administration access was denied because the call originated from an unautho-rized number (RemoteOrigina-tion). Remote Control Terminated <start time>,<end time>, <num>, <RemoteCode>, <ser-vice>, 0Remote administration session from <num> ended. Session length is indicated by start time and end time.Errors Reported by the Status Program[<port><i>] ERR: Problem at Port <num>X A Layer 1 or Layer 2 error oc-curred on <num>.<i> indicates error type:A Layer 1 error ; Layer 2 error 0 Layer 1&2 op-erational.4 RSSI (for mo-bile only)If the error persists, a differenti-ation is possible through 'status of the ports'.If this message appears, status inquiry connections via remote administration are accepted and NMS downloads the proto-col.log file.NOTE: If the RSSI falls below the value configured in the pabx.cfg, the port will shut down automatically.Attention: No Callback-Call <num> ArrivedCallback with DTMF: the Call-back Provider <num> did not call back within approx. 20 sec.Direct Line Access with DTMF: the call was accepted but dis-connected again within x sec. (as defined by MapCallBack-WaitDisc).Table 10.1 Event log messages (continued)Message NMS Definition

10 System maintenance and software updatePage 150CELLX 16.2[99]ERR: SimUnit !connect An outgoing connection to the vGATE SIM Unit could not be established. [99]ERR: ControlUnit <ip addr> !connect An outgoing connection to the vGATE Control Unit could not be established. Number Portability[99i]ERR: np !connect Connection to the iMNP could not be estab-lished. [99i]ERR: np connect <ip addr> Connection to the iMNP reestablished. System Kernel (e)task <name> suspended specified task was suspended due to internal er-ror; host might reboot this port.Mail (f)cdr !connect <ip addr> sending CDR: TCP connect to specified IP ad-dress failed.mail !connect <ip addr> sending e-mail: TCP connect to specified IP ad-dress failed.Radius (g)!DNS-lookup <hostname> DNS lookup for specified host name failed (DNS not activated? Missing or invalid DNS server?).timeout auth <ip addr> Authentication request to specified Radius server failed due to timeout.timeout acnt <ip addr> Accounting request to specified Radius server failed due to timeout.!rsp-auth <ip addr> Response authenticator from specified Radius server was invalid (wrong secret/password?).!auth <ip addr> <num> Authentication denied by specified Radius server.Configuration Errors in the ip.cfgError in ip.cfg line <line>: section [<section_name>] unknownError in ip.cfg line <line>: parameter "<parameter_name>" in [<section_name>] unknownError in ip.cfg line <line>: parameter "<parameter_name>" does not belong to any SectionThere is an error in the NAT ConfigurationThe NAT was not loaded, please check the Configuration for mistakesThere is an error in the DHCPD ConfigurationThe DHCP SERVER was not loaded, please check the Configuration for mistakesThere is an error in the ALTQD ConfigurationThe ALTQD SERVER was not loaded, please check the Configuration for mistakesThere is an error in the FIREWALL ConfigurationThe FIREWALL was not loaded, please check the Configuration for mistakesError in <dsl_interface> Connection failed. Please, connect a cable in the <ethernet> portTable 10.3 Protocol log status and error messages (continued)Message Definition

10 System maintenance and software updatePage 151CELLX 16.210.3 Software updateYou may find that you would like to implement features that are only possible with a morerecent software version. To update the software on your system, follow these instructions:1. To get the necessary software files for your system, you need to contact your localsales representative.2. To update your system software, download the following software files to your harddisk:startnetbsdznetbsdfs.gzip4.vndnetbsdixgate.vndand one of the following:CELLX GSM: igate.tz1 orCELLX CDMA: cgate.tz1 orCELLX UMTS: igate.tz13. To update your GUI, download the following software files to your hard disk:httpd.izghttpd.tz24. Start GATE Manager and connect to the system you want to update.5. Check the software version running on your system to make sure the one you wantto install is newer.6. In the navigation bar, click Directory.7. Right-click the Directory window and click Send To System.8. Once the files have been completely transferred, check the file size and reboot thesystem.Error in <dsl_interface>: Connection Failed. Please, revise your Username/Password configurationError in <dsl_interface>: Connection Failed. Please, revise the DSL ModemTable 10.3 Protocol log status and error messages (continued)Message DefinitionFollow the below listed hints:• Make sure no traffic is running on the system while updating the system. Do not turn the system off during the update.• Never mix the different driver versions.• Make sure there is enough available memory for the new version. We recommend that you delete unnecessary log files and backups.• Do NOT delete or rename existing software files before updating.• Upload the new files ONLY via GATE Manager. Do not use any other process (e.g. FTP) to update the software files. This can lead to irreversible damage to the operating system.• If an error message appears during the update process, do NOT restart or turn off the sys-tem! Make a note of the error message and the update steps that have been taken and contact TELES service.!!

10 System maintenance and software updatePage 152CELLX 16.29. As soon as you can reach the system via GATE Manager again, check the versionnumber of the running software.An update of the following optional function modules occurs in the same way. For a descrip-tion of how to update the software, please refer to Chapter 10.3 Software update.Make sure the file extension has the same running number as that of the file on the system:SNMP agent: snmpd.tz0DNS forwarder: dnsmasg.tz2IP update - DynDNS client: ipupdate.tz2Since these features are only required in individual cases, they are not part of the default soft-ware packet. They can be installed as stand-alone modules for the desired function. The de-scription of the functionality of individual modules appears in their respective chapters.Following completion of transmission, you must adjust the module’s configuration and re-boot the CELLX. Once you have rebooted the system, you can use the required features.10.4 SNMP agentThis module allows you to connect the systems and their functions to an SNMP-based net-work monitoring system. With this module, SNMP requests are answered and alarm messag-es (for example Layer 1 errors on E1 lines) and error recovery messages are sent via SNMP trap.The trap consists of a generic trap linkUp or linkDown, and a specific trap.Table 10.4 contains a list of the most easily verifiable specific traps: These files form a unit and belong to the same software version. To avoid compatibility conflicts, check with TELES service before you update the software.iiThe following software package must be installed: snmpd.tz0.iiTable 10.4 Specific trap Error Code Definition0 Port registered/up1Wrong PIN4Bad RSSI7Unknown error, port restarted9 Port restart11 Layer 2 problem12 SIM blocked14 SIM barred

10 System maintenance and software updatePage 153CELLX 16.2SNMP requests retrieve the value of a variable or list of variables (GET/GETBULK) referred toas OIDs. Each OID identifies a variable that can be read via SNMP, as described in Table 10.5.17 Layer 1 problem / port down18 SIM missing21 Registration failed39 Call limit reached40 SMS limit reached41 Assign limit reached42 SIM inserted47 ACD limit reached48 SIM removed0eth0 / eth1 up52 eth0 / eth1 downTable 10.4 Specific trap (continued)Error Code DefinitionTable 10.5 Description of OIDs OID Description Type1.3.6.1.4.1.2170.1.2.1.1.1 Port number INTEGER1.3.6.1.4.1.2170.1.2.1.1.2 Port address DisplayString1.3.6.1.4.1.2170.1.2.1.1.3 Port type DisplayString1.3.6.1.4.1.2170.1.2.1.1.4 State of port line 1 DisplayString1.3.6.1.4.1.2170.1.2.1.1.5 State of port line 2 DisplayString1.3.6.1.4.1.2170.1.2.1.1.6 Number of currently active con-nections on portINTEGER1.3.6.1.4.1.2170.1.2.1.1.7 Overall state of port INTEGER1.3.6.1.4.1.2170.1.2.1.1.8 Calls rejected due to no chan-nel availableINTEGER1.3.6.1.4.1.2170.1.2.1.1.9 Calls rejected due to busy INTEGER1.3.6.1.4.1.2170.1.2.1.1.10 Calls rejected due to no user INTEGER1.3.6.1.4.1.2170.1.2.1.1.11 Calls disconnected INTEGER1.3.6.1.4.1.2170.1.2.1.1.12 Outgoing calls INTEGER1.3.6.1.4.1.2170.1.2.1.1.13 Incoming calls INTEGER1.3.6.1.4.1.2170.1.2.1.1.14 Channels in use more than 90 percentINTEGER1.3.6.1.4.1.2170.1.2.1.1.15 Accumulated call duration INTEGER

10 System maintenance and software updatePage 155CELLX 16.2The following settings are possible in the [snmpd] section in the pabx.cfg file: 10.5 DNS forwarderWith this module, the system can function as a DNS server for the clients in the local network.The system in the local network sent the DNS query to the CELLX, which forwards the queriesto a known DNS server address if no valid entry for the query is known. The advantage is that the clients always enter the CELLX’s address as DNS server address, sothat no public DNS server address is required. The CELLX functions in this scenario as a router. Of course, the DNS server’s address can also be transmitted to the clients using the integratedDHCP server. If the CELLX is used as a DSL router or if it sets up a dial-up connection, no entryis required in the pabx.cfg for the parameter NameServer. The DNS server’s address that isnegotiated through this connection will be used.Table 10.7 Settings in the [snmpd]section Parameter DefinitionPort=<port> Defines the target port for the get service (de-fault 161). The port for the trap server is fixed at 162.TrapServer=<ip addr> Enter the SNMP trap server’s IP address. Example for listing more than one: TrapServer=192.168.0.10 192.168.0.12Community=<password> Enter a password for a community (group). The default password is public.The current implementation evaluates the con-figured password only when sending a trap. GET requests use the default value.Example 10.2 Settings in the [snmpd]section[snmpd]TrapServer=192.168.0.1Community=ABCDEThe following software package must be installed: dnsmasg.tz2.ii

10 System maintenance and software updatePage 156CELLX 16.210.6 ipupdate - DynDNS clientThis function allows you to assign a defined hostname to an IP address that changes dynam-ically. That means that you can always reach a device or service through the public IP network,even if, for example, it is a common DSL connection with dynamic IP address allocation. Sev-eral providers support this service.Make the following entries in the system’s pabx.cfg, in the [DynDNS] section: The following software package must be installed: ipupdate.tz2.iiTable 10.8 pabx.cfg: DynDNS DynDNS Parametersservice=<type>Specifies which provider is used. The following providers are supported:dhsdyndnsdyndns-staticdynsezipeasydnseasydns-partnergnudipheipv6tbhnpgpowodstzozoneedithttp://www.dhs.orghttp://www.dyndns.orghttp://www.dyns.cxhttp://www.ez-ip.nethttp:/www.easydns.comhttp://www.gnudip.cheapnet.nethttp://www.hn.orghttp:www.justlinux.comhttp://ods.orghttp://www.tzo.comhttp://zoneedit.comuser=<username:password>Defines the username and password for the DNS service provider.host=<domain_name_of_dns_service>Enter the domain name that is used.interface=<If>Defines the interface to be used. Possible entries are emac0, emac1, pppoe0. The dynamic IP ad-dress for this interface is transmitted to the service provider.max-interval=<sec>Defines the value in seconds in which actualization of the name in the DNS database must occur. 2073600 seconds (24 days) is the default value. The shortest interval allowed is 60 seconds. Bear in mind that this setting may cause the provider to block the domain name, since multiple regis-trations in short intervals are often not allowed. You must clear this with your provider.

10 System maintenance and software updatePage 157CELLX 16.2In the following example, the DynDNS service is used and the domain name is host.do-main.de; the username is user and the password is pwd. The CELLX works as DSL router andthe dynamically allocated IP address of the PPPoE interface is used.Included in the possible uses for this feature is remote access to the CELLX when the IP con-nection does not have a fixed IP address. In this case, you can access the system, for examplewith the GATE Manager, if the host name is used in the Remote Number dialog. Example en-try in the Remote Number dialog: IP:host.domain.de.10.7 TraceDuring operation, the trace readouts of the CELLX can be saved in a file or transmitted withremote maintenance directly. The trace options must be turned on in the GATE Manager (of-fline or online trace) or via FTP raw commands (see Chapter 4.10.3 FTP). Trace results present-ed here are for PRI,VoIP, GSM/CDMA/UMTS interfaces and for the following services invarious levels:Example 10.3 DynDNS[DynDNS]service=dyndnsuser=user:pwdhost=host.domain.deinterface=pppoe0max-interval=2073600Table 10.9 Trace optionsOption DefinitionMail Output for all SMTP packets.NumberPortability Output of all packets for communication with the iMNP.VoiceCodecs Output of RTCP information described under VP module.PPP Output of PPP connection information.DTMF Output for DTMF tone detection.Remote Output for GATE Manager and NMS communi-cation. For offline traces only.

10 System maintenance and software updatePage 158CELLX 16.2Figure 10.1 GATE Manager: online trace activation windowCELLXs offer two different types of trace:Online - trace information is immediately displayed in the GATE Manager’s tracewindow.Offline - trace information is written to a file on the CELLX.CELLX systems create trace files when the TraceLog=file entry is present in the pabx.cfg. Trac-es can be activated via remote administration (GATE Manager or FTP). The following table describes the fields that are on the online trace activation window. Foroffline traces, some fields are not provided.Table 10.10 Online trace activation window Field DescriptionTrace TypeLayer 2 and 3 Select this option if the trace is to contain layer 2 and 3 messages.Layer 3 only Select this option if the trace is to contain layer 3 messages only.DSS1/NI2 Select this option if the trace is to contain DSS1/NI2 messages only.SS7 For SS7 messages, select this option.Translate TraceLayer 2 To translate layer 2 messages into plain text, select this option.Layer 3 To translate layer 3 messages into plain text, select this option.Local Trace FileCreate Trace File Check this box if you want to store a trace file locally on your computer.File Name Click this button to change the default directory and file name of the local trace file.

10 System maintenance and software updatePage 159CELLX 16.2Trace output formatThe following entries appear at the beginning and end of each trace:DD.MM.YY-hh:mm:ss.ss, StartDD.MM.YY-hh:mm:ss.ss, End– DD = day– hh = hour– MM = month– mm = minute– YY = year– ss.ss = hundredths of secondsPorts to TraceAll Select this option to trace all ports.Only Port Number Enter here the port which you want to trace.Port Mask Select from this port mask which ports you want to trace.IP TraceMail, Number Portability, vGATE, ...Contains a list of port-independent trace options. The different options can be limited to error messages, debug messages, or detailed trace output. The Advanced field is for TELES support usage only. For an explanation of the different trace option please refer to Chapter 10.9 Trace options on page 157.CASR2Timeslots Select which of the channels you want to trace for the CASR2 ports.General Trace Check this box if you want to run a general trace for the different timeslots.Level Select which special type of information you want to trace for the dif-ferent timeslots.Additional The following additional entries are possible. The number behind the colon referes to the trace level. 0 = no traces, 1 = few traces, 2 = many traces, 3 = very many traces (only nstanl).autodial:0 for auto dial trace messagesfctrans:trclevel=debug for ISDN facility to SIP converter messagesnstanl:0 for call routing trace messagesradius:0 for RADIUS trace messagesrtman:0 for routing manager trace messagess0:0 for BRI trace messagess2m:0 for PRI and switching matrix trace messagesvoip:noreg to suppress traces of REGISTER and responsesPlease bear in mind that the volume of trace readouts can grow quite large, so that faulty transmission of the trace data may result with remote maintenance. A trace at full capacity can cause the system to crash.Table 10.10 Online trace activation window (continued)Field Descriptionii

10 System maintenance and software updatePage 160CELLX 16.2Traces appear in the following format:[<hh:mm:ss>] <module>[<port>]: <trace><module> – s = send for PRI/BRI or mobile ports– r = receive for PRI/BRI or mobile ports– x = send to VoIP destinations– y = receive from VoIP destinations– i = information messages and internal trace outputs between VoIP and the otherinterfaces (ISDN, mobile)– a = VoIP controllers RTCP output–m = mail output– g = remote output<port> – port number (controller number in the pabx.cfg) or 255 if a service is used<trace>– output in the defined syntax for the module10.7.1 ISDN trace outputTrace output for DSS1 are in hexadecimal notation. You can use the external tool Trace-View.exe to translate offline trace output. You will find the tool in the Software folder onthe enclosed CD. The GATE Manager’s trace window can also display translated online traces.The following example shows an untranslated DSS1 trace.Example 10.4 ISDN trace output17.05.06-09:54:40,Start 11.7a (L3)[09:55:14.58] r[00]: 00 01 02 02 08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 6c 02 81 31 70 06 81 31 32 33 34 35 7d 02 91 81 [09:55:14.58] s[00]: 02 01 02 04 08 02 80 02 0d 18 03 a9 83 81 [09:55:14.58] s[01]: 00 01 a8 9a 08 02 00 46 05 04 03 80 90 a3 18 03 a1 83 89 6c 02 81 31 70 06 81 31 32 33 34 35 7d 02 91 81 [09:55:14.58] r[01]: 02 01 9a aa 08 02 80 46 0d 18 03 a9 83 89 [09:55:14.86] r[01]: 02 01 9c aa 08 02 80 46 01 [09:55:14.86] s[00]: 02 01 04 04 08 02 80 02 01 [09:55:16.73] r[01]: 02 01 9e aa 08 02 80 46 07 29 05 05 07 01 09 33 4c 07 01 81 31 32 33 34 35 [09:55:16.73] s[01]: 00 01 aa a0 08 02 00 46 0f [09:55:16.73] s[00]: 02 01 06 04 08 02 80 02 07 29 05 05 07 01 09 32 4c 07 01 81 31 32 33 34 35[09:55:16.73] r[00]: 00 01 04 08 08 02 00 02 0f [09:55:44.30] r[00]: 00 01 06 08 08 02 00 02 45 08 02 80 90 [09:55:44.35] s[01]: 00 01 ac a0 08 02 00 46 45 08 02 80 90 [09:55:46.71] r[01]: 02 01 a0 ae 08 02 80 46 4d [09:55:46.71] s[01]: 00 01 ae a2 08 02 00 46 5a [09:55:46.71] s[00]: 02 01 08 08 08 02 80 02 4d [09:55:46.71] r[00]: 00 01 08 0a 08 02 00 02 5a 17.05.06-09:51:33,End

10 System maintenance and software updatePage 161CELLX 16.210.7.2 GSM/CDMA/UMTS trace outputThe trace output for GSM appears in hexadecimal notation. Its format is the same as that forISDN output. Table 10.11 and Table 10.12 describe the contents of GSM trace output. Table 10.11 Request messages to the GSM module Hex Value Description00 Setup01 Connect02 Disconnect03 SMS04 DTMF05 Set Config06 Get Config07 LED08 Restart09 Switch SIMTable 10.12 Incoming, indication message from the GSM module Hex Value Description0B Alert0C Voice Indication0D Connect0E DTMF0F Setup10 Disconnect11 SMS12 SMS Confirmation13 Error16 Get Config Confirmation18 Dial-End Call Proceeding19 USSD1A Restart Indication

10 System maintenance and software updatePage 162CELLX 16.2The following example shows a GSM call through the fourth GSM controller.10.7.3 VoIP trace outputAs described above in Chapter 10.7 Trace, there are four modules for VoIP traces. The groupsx (send), y (receive) and i (information and internal output) appear when a Layer2 or Layer3offline or online trace is started. Group a (RTCP output) only appears when the module VoiceCodecs is active.Particularly in the case of VoIP connections (protocols H.323 and SIP), the trace output is quiteextensive and abbreviations make it difficult to keep track of the results. The following listcontains a description of H.323 output. Output for the signaling protocol SIP is transmitted in ASCII and translated for better legibility.Since they are displayed unabridged, no description is necessary. Information and internaloutput traces correspond with the H.323 output and are described in the following tables.For ENUM, please refer to Chapter 10.7.3.5 ENUM output.In general, the following rules apply for this trace output: The information is thoroughly analyzed where it is received (all rcv messages). Example 10.5 GSM call through fourth GSM controllerStatus Request[14:57:51.80] s[04]: 06Status Information: [14:57:51.80] r[04]: 16 Setup Request:[14:57:52.29] s[04]: 00 4c 93 04 00 00 00 35 36 36 37 00 35 38 2c 36 34 36 2c 33 30 2c 2c 2c 30 2c 2c 2c 30 2c 32 36 32 2c 30 37 2c 00 72 64 09 75 70 20 7b 64 35 7d 20 27 2e 2e 2b 43 43 45 44 3a 20 32 36 32 2c 30 37 2c 34 Dial End:[14:57:55.47] r[04]: 18 Alert:[14:57:55.63] r[04]: 0b Connect Indication:[14:57:56.63] r[04]: 0d Disconnect Request:[14:59:54.13] s[04]: 02 4c 93 00 Disconnect Indication:[14:59:54.19] r[04]: 10Table 10.13 H.323 output Packet Descriptionh225 H.225-protocol messages.h245 H.245-protocol messages.pstn Messages of the internal protocol interface that provides the interface to the other interfaces PRI, BRI and GSM.rcv Coming from the IP network or the internal pro-tocol interface; appears with <dir> in the trace lines.snd Sending to the IP network or the internal proto-col interface; appears with <dir> in the trace lines.

10 System maintenance and software updatePage 163CELLX 16.210.7.3.1 Interface IP networkEstablish H.323 sessionUsually there is trace output that displays a new H.323 session. The direction is crucial (wheth-er the call is going into or coming out of the IP network).The outut syntax is h225connect to <ip address> cr <cr> s <si> for calls going intothe IP network and h225accept from <ip address> s <si> for calls coming out of theIP network.H.225 signaling outputThe following trace results are for a call coming from the IP network. rcv will appear at <dir>and signifies the direction: h225<dir> tpkt msg 0x<mt> h225cr <cr> addr <ip ad-dress>.Table 10.14 H.323 session Trace Output Descriptionconnect to Outgoing VoIP callaccept from Incoming VoIP call<ip address> Peer's IP addresscr <cr> Call reference (corresponds with the internal protocol interface's PSTN call reference)s <si> Session IDTable 10.15 H.225 signaling Trace Output Description<mt> The ETS message type in hexadecimal; can con-sist of values listed in Table 10.16.<hcr> H.225 call reference in hexadecimal (does not have to be unique when calls come from multiple peers).<ip address> The peer's IP address.Table 10.16 ETS message types Hex Value Message Type1 Alerting2Call Proceeding3 Progress5Setup7 ConnectDSetup Acknowledge

10 System maintenance and software updatePage 164CELLX 16.2The following lines show the packet contents in detail:h225 decode rc 0, q931 msg 0x<mt> = 0, len <length>h225<type> <mt> voipcfg addr <ip address> rc 0 compr <codec>h225<type> <mt> h225cr <hcr> FS:<bool> (<codec>,<ip address>,<port>)TUNN:<bool> H245:<bool>(<ip address>,<port>)h225<type> <mt> h225cr <hcr> cr <cr>5A Release Complete62 Facility6E Notify7B Information7D StatusTable 10.16 ETS message types (continued)Hex Value Message TypeTable 10.17 Incoming VoIP calls Trace Output Description<mt> Message type in hexadecimal as per ETS stan-dard (see Table 10.16) or written out as a name.len <length> Packet length in bytes.h225<type> H.225 rcv or send; received or sent from the IP network.addr <ip address> Peer's IP address.compr <codec> Peer's compression list (see Table 10.18).FS<bool> FastStart offered in the signaling packet or not.(<codec>, Lists codecs offered (seeTable 10.38).<ip address>, Peer's IP address for RTP data.<port>) Peer's port for RTP Data.Tunn<bool> Shows whether or not tunneling is offered as a signaling variant.H245<bool> Shows an extra H.245 session.(ip address, Peer's IP address.port) Peer's port.h225cr <hcr> H.225 message's call reference (does not have to be unique when calls come from multiple VoIP peers).cr <cr> Internal call reference (always unique for the call).

10 System maintenance and software updatePage 165CELLX 16.2When the call is sent in the direction of the IP network, the trace will include only the mostimportant information: h225<type> <mt1> dad <num> cr <cr>.Table 10.18 Compression codecs used Synonym CodecA G.711Alaw64kBG.711Ulaw64kC G.7231DG.728E G.729FgsmFullRateG T.38faxOG.729AP G.72616QG.72624R G.72632SG.729BT G.729ABUG.729EV G.723LWTransparentX G.721YiLBC20ZiLBC30Table 10.19 Calls to the IP network 1 Trace Output Description<mt> Message type written out; if a decimal number appears here, it will be translated as per Table 10.16.<num> Called party number.<cr> Call reference.

10 System maintenance and software updatePage 166CELLX 16.2Or: h225<type> callproc typ <mt> cr <cr>.RTP/RTCP outputThe RTP/RTCP output displays whether the signaling information corresponds with the con-tents of the compression chips. The output occurs when a media channel is set up or torndown:rtp start cr <cr> ch <ch> li <li> ri <ri> st <st> fx <fx> cp <comp> txm<factor>.The RTP stop message has the following syntax: rtp stop cr <cr>1 ch <ch>.The following output shows the RTCP packet statistics:Table 10.20 Calls to the IP network 2 Trace Output Description<mt> The ETS message type in hexadecimal.<cr> Call reference.Table 10.21 RTP/RTCP output Trace Output Description<cr> Call reference.<ch> The internal media channel used.<li> 1 appears when the local RTP address (and port) has been defined.<ri> 1 appears when the remote RTP address (and port) have been established.<st> 0 appears if the channel's voice packetizer has not yet been started. 1 appears if the voice pack-etizer can receive, but not send. 2 appears when the voice packetizer can receive and send.<fx> 1 appears when T.38 (fax) is used, otherwise 0.<comp> The codec used, as per Table 10.18.<factor> Multiplication factor for default frame size (20ms, 30 ms for G.723).Table 10.22 RTP stop message Trace Output Description<cr> Call reference.<ch> The internal media channel used.

10 System maintenance and software updatePage 167CELLX 16.2rtcp <ch>: SR <dir> pc <pc> oc <oc> ji <ji> rt <rt> fl <fl> cl <cl>.The following output shows the jitter buffer status:a[<controller>]: <VoIPcodecChipType> ch <ch> jitter buffer n1 n2 n3n4 n5n6 n7 n8.An RTP connection has ended when the following trace output appears:Table 10.23 RTCP packet statistics Trace Output Description<ch> The internal media channel used.SR<dir> Rx sender report (received) is more interesting, since it comes from the peer. Tx sender report (transmitted).<pc> Packet count (number of packets transmitted/re-ceived).<oc> Octet count (number of octets transmitted/re-ceived).<ji> Delay jitter [msec].<rt> Round-trip local<->remote, round-trip delay [msec].<fl> Fraction lost: Fraction of packets lost [8lsb].<cl> Cumulative lost: number of lost packets [24lsb].Table 10.24 Jitter buffer status Trace Output Descriptionn1 SteadyStateDelay in millisecondsn2 NumberOfVoiceUnderrunn3 NumberOfVoiceOverrunn4 NumberOfVoiceDecoderBfi (bfi = bad frame in-terpolation)n5 NumberOfVoicePacketsDroppedn6 NumberOfVoiceNetPacketsLostn7 NumberOfIbsOverrun (ibs = in band signaling)n8 NumberOfCasOverrun

10 System maintenance and software updatePage 168CELLX 16.2a[<controller>]: <VoIPcodecChipType> stop ch=<ch>.The following output results when the codec changes for a fax connection: a[<controller>]: ac49x ch <ch> fax/data n1 n2 n3.Table 10.25 RTP stop message (VP module) Trace Output Description<ch> The internal media channel used.Table 10.26 Codec change for fax Trace Output Descriptionn1 Fax bypass flag:0Voice, data bypass or fax relay1Fax bypassn2 Signal detected on decoder output (see Table 10.27)n3 Signal detected on encoder input (see Table 10.27)Table 10.27 fax or data signal event Value Definition Description0SILENCE_OR_UNKNOWN Undefined (unknown signal or silence)1FAX_CNG CNG-FAX (calling fax tone, 1100 Hz)2ANS_TONE_2100_FAX_CED_OR_MODEMFAX-CED or modem-ANS (an-swer tone, 2100 Hz)3ANS_TONE_WITH_REVERSALS ANS (answer tone with rever-sals)4ANS_TONE_AM ANSam (AM answer tone)5ANS_TONE_AM_REVERSALS ANSam (AM answer tone with reversals)6FAX_V21_PREAMBLE_FLAGS FAX-V.21 preamble flags7FAX_V8_JM_V34 FAX-V.8 JM (fax call function, V.34 fax)8VXX_V8_JM_VXX_DATA V.XX-V.8 JM (data call func-tion, V-series modem)9V32_AA V.32 AA (calling modem tone, 1800 Hz)10 V22_USB1 V.22 USB1 (V.22(bis) unscram-bled binary ones)

10 System maintenance and software updatePage 169CELLX 16.2Fax relay is activated for the corresponding channel:a[<controller>]: Ac49xActivateFaxRelayCommand(1) ch <ch> rc <cr>.The following output shows various values for fax transmission (see Table 10.28 for a descrip-tion of the values):a[<controller>]: ac49x ch <ch> faxrelay: n1 n2 n3 n4 n5 n6 n7 n8 n9 n10 n11n12 n13 n14 n15 n16 n17.11 V8_BIS_INITIATING_DUAL_TONEV.8bis initiating dual tone (1375 Hz and 2002 Hz)12 V8_BIS_RESPONDING_DUAL_TONEV.8bis responding dual tone (1529 Hz and 2225 Hz)13 VXX_DATA_SESSION V.XX data session14 V21_CHANNEL_2 V.21 channel 2 (mark tone, 1650 Hz)15 V23_FORWARD_CHANNEL V.23 forward channel (mark tone, 1300 Hz)16 V21_CHANNEL_1=18 V.21 channel 1 (mark tone, 980 Hz)17 BELL_103_ANSWER_TONE Bell 103 answer tone, 2225 Hz18 TTY TTY19 FAX_DCN FAX-DCN (G.3 fax disconnect signal)Table 10.27 fax or data signal event (continued)Value Definition DescriptionTable 10.28 Fax status Value Field Name Descriptionn1 UnableToRecoverFlag (0 no, 1 yes) Unable to recover lost packetn2 IllegalHdlcFrameDetectedFlag (...) Illegal HDLC frame detectedn3 FaxExitWithNoMcfFrameFlag Fax exit with no MCF Framen4 HostTransmitOverRunFlag Channel received a buffer overrunn5 HostTransmitUnderRunFlag Channel received a buffer underrunn6 InternalErrorFlag Internal errorn7 ReceivedBadCommandFlag A bad command was received. Words 8 and 9 describe the bad command n8 TimeOutErrorFlag A timeout error occurred

10 System maintenance and software updatePage 170CELLX 16.2n9 T30RxState T.30 receive state0 Init (initialization state)1 CNG (calling tone)2 CED (called terminal identifica-tion)3 V21 (switch to V21)4 NSF (non-standard facilities)5 NSC (non-standard (facilities) command)6 CSI (called subscriber identifi-cation)7 CIG (calling subscriber identifi-cation)8 DIS (digital identification signal)9 DTC (digital transmit com-mand)10 NSS (non-standard services)11 TSI (transmitting subscriber ID)12 DCS (digital command signal)13 CTC (continue to correct)14 CRP (command repeat)15 DCN (disconnect)16 Pre-message response17 Post-message response18 Post-message command19 VXX (receive illegal high-speed signal)20 TCF (training check function21 Fax image22 V.8 CI (calling indicator (re-served))23 V.8 CM (calling menu)24 V.8 (joint menu)n10 T30TxState T.30 transmit state. For values, see the entry for T30RxState above.n11 NumberOfTransferredPages Number of transmitted or received pag-es positively confirmed by answering fax.n12 BadInputPacketId Sequence number of Bad Input UDPTL packet, or the first two bytes of the in-put TCP packet. The field is relevant if the “Bad CMD” or the “Unable Recov-er” bit is set.n13 BadInputPacketTotalSize The total number of bytes in a bad fax packet.n14 FaxBitRate 0 Undefined or 300 bpx (T.30 control signals)1 2400 bps2 4800 bps3 7200 bps4 9600 bps5 12000 bps6 14400 bps7-15 ReservedTable 10.28 Fax status (continued)Value Field Name Description

10 System maintenance and software updatePage 171CELLX 16.2The following output appears when the compression chip detects DTMF tones:a[<controller]: ac49x ch <ch> ibs <dtmf> <dir> <mode> <lev> <dur>.10.7.3.2 Internal protocol interface (to ISDN, mobile)These trace outputs always begin with the keyword pstn, followed by the direction and themessage type. The message is then either concluded or other information follows: n15 DemodulationStatus 0 EQM and Timing Off-set fields are invalid. 1 EQM and Timing Off-set fields are valid.n16 EyeQualityMonitor (EQM) Eye Quality Monitor measure for TCF or fax image. The value of 0 corresponds to the best quality of demodulation. Values greater than 100 have a nega-tive influence on the quality of the fax image.n17 TimingOffsetPpm Timing Offset (ppm) recovered during demodulation of TCF or fax image. The offset is a short integer equal to the sum of the sampling rate error and the sending fax baud rate offset. The value is in integers and and may not exceed 50 ppm in the following ranges during fax transmission (T30TxState): 65535 – 65486 (-50ppm) 0 – 50 (+50ppm)Table 10.28 Fax status (continued)Value Field Name DescriptionTable 10.29 DTMF tone detectionTrace Output Description<ch> Media channel<dtmf> Detected DTMF tone in the stream or as per RFC2833<dir> Direction0Coming from BRI/analog1Coming from VoIP<mode> 0Tone has ended1Tone has been detected<lev> Signal level in -dBm<dur> Tone duration

10 System maintenance and software updatePage 174CELLX 16.2The output syntax for the logical channel parameters is as follows:OpenLogicalChannel cn=<cn> cpr=<comp> sessid=<sid> ctrl=<ip address>:<rtcpport>OpenLogicalChannelAck cn=<cn> sessid=<sid> media=<ip address>:<rtp port>The trace output is as follows when the message type is not translated or is ignored:h245<dir>(<tt>) cr <cr> unknown msg <hmt> <hmi>Table 10.35 Logical channel parameters Trace Output Description<cn> H.245 channel number per H.225 connection.<sid> Session ID.<comp> Codec used (see Table 10.18).<ip address> Protocol peer IP address.<rtcp port> Port used for the protocol RTCP.<rtp port> Port used for the protocol RTP.Table 10.36 H.245 parameters Trace Output Descriptionhmt The H.245 message type (multimedia system control message type), (Table 10.37).hmi The H.245 message ID (see Table 10.38, Table 10.39, Table 10.40, Table 10.41).Table 10.37 Multimedia system control message types ID Message0 (Table 10.38) Request1 (Table 10.39)Response2 (Table 10.40) Command3 (Table 10.41)Indication

10 System maintenance and software updatePage 175CELLX 16.2Depending on the system control message type, one of the following message IDs appear: Table 10.38 Message IDs for request message ID Message0 NonStandard1MasterSlaveDetermination2 TerminalCapabilitySet3OpenLogicalChannel4 CloseLogicalChannel5RequestChannelClose6 MultiplexEntrySend7RequestMultiplexEntry8 RequestMode9RoundTripDelayRequest10 MaintenanceLoopRequest11 CommunicationModeRequest12 ConferenceRequest13 MultilinkRequest14 LogicalChannelRateRequestTable 10.39 Message IDs for response message ID Message0 NonStandard1MasterSlaveDeterminationAck2 MasterSlaveDeterminationReject3TerminalCapabilitySetAck4 TerminalCapabilitySetReject5OpenLogicalChannelAck6 OpenLogicalChannelReject7CloseLogicalChannelAck8 RequestChannelCloseAck9RequestChannelCloseReject10 MultiplexEntrySendAck11 MultiplexEntrySendReject12 RequestMultiplexEntryAck

10 System maintenance and software updatePage 176CELLX 16.213 RequestMultiplexEntryReject14 RequestModeAck15 RequestModeReject16 RoundTripDelayResponse17 MaintenanceLoopAck18 MaintenanceLoopReject19 CommunicationModeResponse20 ConferenceResponse21 MultilinkResponse22 LogicalChannelRateAcknowledge23 LogicalChannelRateRejectTable 10.40 Message IDs for command message ID Message0 NonStandard1MaintenanceLoopOffCommand2 SendTerminalCapabilitySet3EncryptionCommand4 FlowControlCommand5EndSessionCommand6 MiscellaneousCommand7CommunicationModeCommand8 ConferenceCommand9h223MultiplexReconfiguration10 NewATMVCCommand11 MobileMultilinkReconfigurationCommandTable 10.41 Message IDs For indication message ID Message0 NonStandard1FunctionNotUnderstood2 MasterSlaveDeterminationRelease Table 10.39 Message IDs for response message (continued)ID Message

10 System maintenance and software updatePage 177CELLX 16.210.7.3.4 RAS (registration, admission, status)As a general rule, the most important terminal and gatekeeper messages appear written outwith the gatekeeper's IP address (<ip addr>).Here is the output syntax for gatekeeper discovery requests:H225 GatekeeperRequest to <ip addr> (s 131)H225 GatekeeperConfirm <ip addr>H225 GatekeeperReject <ip addr> reason <reason> Here is the output syntax for endpoint registration requests:3TerminalCapabilitySetRelease4 OpenLogicalChannelConfirm5RequestChannelCloseRelease6 MultiplexEntrySendRelease7RequestMultiplexEntryRelease8 RequestModeRelease9MiscellaneousIndication10 JitterIndication11 h223SkewIndication12 NewATMVCIndication13 UserInput14 h2250MaximumSkewIndication15 McLocationIndication16 ConferenceIndication17 VendorIdentification18 FunctionNotSupported19 MultilinkIndication20 LogicalChannelRateRelease21 FlowControlIndication22 MobileMultilinkReconfigurationIndicationTable 10.41 Message IDs For indication message (continued)ID MessageTable 10.42 RAS Trace Output Description<reason> Gatekeeper reject reason, see Table 10.46.

10 System maintenance and software updatePage 178CELLX 16.2H225 GkRegistration to <ip addr>H225 RegistrationConfirm <ip addr>H225 RegistrationReject <ip addr> reason <reason>Below you see the output syntax for bandwith availability indication:H225 GkResourcesAvailableIndicate to <ip addr> (<act chan> <max chan>)H225 ResourcesAvailableConfirm <ip addr>Here is the output syntax for call admission requests:H225 GkAdmission cr <cr> to <ip addr>H225 AdmissionConfirm <ip addr> cr <cr>H225 AdmissionReject <ip addr> reason <reason>Here is the output syntax for call teardown requests:H225 GkDisengage cr <cr> to <ip addr>H225 DisengageConfirm <ip addr>Here is the output syntax for registration release requests:H225 UnregistrationRequest <ip addr>H225 GkUnregistrationConf to <ip addr>All other messages appear as follows:H225 unknown msg from Gk <ip addr>: <code>Table 10.43 Gatekeeper 1 Trace Output Description<reason> Registration reject reason, see Table 10.47.Table 10.44 Gatekeeper 2 Trace Output Description<reason> Admission reject reason, see Table 10.48.Table 10.45 Gatekeeper 3 Trace Output Description<code> Unknown gatekeeper message, see Table 10.49.

10 System maintenance and software updatePage 179CELLX 16.2Table 10.46 Gatekeeper reject reason ID Reject Reason0 resourceUnavailable1terminalExcluded2 invalidRevision3undefinedReason4 securityDenial5genericDataReason6 neededFeatureNotSupportedTable 10.47 Registration reject reason ID Reject Reason0 DiscoveryRequired1InvalidRevision2 InvalidCallSignalAddress3InvalidRASAddress4 DuplicateAlias5InvalidTerminalType6 UndefinedReason7TransportNotSupported8 TransportQOSNotSupported9ResourceUnavailable10 InvalidAlias11 SecurityDenial12 RullRegistrationRequired13 AdditiveRegistrationNotSupported14 InvalidTerminalAliases15 GenericDataReason16 NeededFeatureNotSupportedTable 10.48 Admission reject reason ID Reject Reason0 CalledPartyNotRegistered1InvalidPermission

10 System maintenance and software updatePage 180CELLX 16.22 RequestDenied3UndefinedReason4 CallerNotRegistered5RouteCallToGatekeeper6 InvalidEndpointIdentifier7ResourceUnavailable8 SecurityDenial9QosControlNotSupported10 IncompleteAddress11 AliasesInconsistent12 RouteCallToSCN13 ExceedsCallCapacity14 CollectDestination15 CollectPIN16 GenericDataReason17 NeededFeatureNotSupportedTable 10.49 Unknown gatekeeper messages ID Message0 GatekeeperRequest1GatekeeperConfirm 2 GatekeeperReject 3RegistrationRequest 4 RegistrationConfirm 5RegistrationReject 6 UnregistrationRequest 7UnregistrationConfirm 8 UnregistrationReject 9AdmissionRequest 10 AdmissionConfirm 11 AdmissionReject 12 BandwidthRequest Table 10.48 Admission reject reason (continued)ID Reject Reason

10 System maintenance and software updatePage 181CELLX 16.210.7.3.5 ENUM outputThis output is assigned to group i and occurs with Layer2 and Layer3 traces:i[<controller>]: enum_query cr <CR> ch <CH>: <num> -> <length> <<answerpattern>>.13 BandwidthConfirm 14 BandwidthReject 15 DisengageRequest 16 DisengageConfirm 17 DisengageReject 18 LocationRequest 19 LocationConfirm 20 LocationReject 21 InfoRequest 22 InfoRequestResponse 23 NonStandardMessage 24 UnknownMessageResponse 25 RequestInProgress 26 ResourcesAvailableIndicate 27 ResourcesAvailableConfirm 28 InfoRequestAck 29 InfoRequestNak 30 ServiceControlIndication 31 ServiceControlResponse Table 10.49 Unknown gatekeeper messages (continued)ID MessageTable 10.50 ENUM output Trace Output Description<cr> Call reference.<ch> Media channel.<num> Phone number converted into ENUM domain format.<length> Length of the answer field in the DNS response in bytes. 0 appears if the number was not found.<answer pattern> Displays the DNS response. 0 appears if the num-ber was not found.

10 System maintenance and software updatePage 182CELLX 16.210.7.3.6 ExamplesThe following examples are offline traces. You can generate them using the GATE Manageror FTP commands. The filename is trace.log. The following cases appear in the examples:Incoming H.323 call with FastStart (please see "Incoming H.323 call with FastStart" onpage 182 )Outgoing H.323 call with FastStart (please see "Outgoing H.323 call with FastStart" onpage 183)Fax call (please see "Fax call" on page 184)Incoming H.323 call with FastStartExample 10.6 Incoming H.323 call with FastStart[15:25:13.65] i[02]: h225accept from 172.16.0.200 s 4[15:25:13.75] y[02]: h225rcv tpkt msg 5 h225cr 8006 addr 172.16.0.200 pt 0[15:25:13.75] y[02]: h225 decode rc 0, q931 msg 5 (0), len 364[15:25:13.75] y[02]: h225rcv setup voipcfg addr 172.16.0.200 rc 0 <DF> compr EABG[15:25:13.75] y[02]: h225rcv faststart <A1B1E1G0>[15:25:13.75] y[02]: h225rcv setup oad 01 00 <111> <> dad 01 <123456> rad <> bc 038090a3 0101[15:25:13.75] y[02]: h225rcv setup h225cr 8006 FS:1(E,172.16.0.200,29000) TUNN:1 H245:0(0,0)[15:25:13.75] y[02]: h225rcv setup h225cr 8006 cr 7[15:25:13.75] i[02]: pstnsnd setup dad 123456 oad 1 cr 7 s 4[15:25:13.75] s[00]: 00 01 52 4c 08 02 00 08 05 04 03 80 90 a3 18 03 a1 83 87 6c 04 81 31 31 31 70 07 81 31 32 33 34 35 36 7d 02 91 81 [15:25:13.75] i[02]: pstnrcv connresp cr 7 acc 5 ch 1[15:25:13.75] x[02]: h225snd callproc typ d cr 7 pri 0[15:25:13.75] r[00]: 00 01 01 54 [15:25:13.75] r[00]: 02 01 4c 54 08 02 80 08 0d 18 03 a9 83 87 [15:25:13.75] s[00]: 02 01 01 4e [15:25:14.33] r[00]: 02 01 4e 54 08 02 80 08 01 [15:25:14.33] s[00]: 02 01 01 50 [15:25:14.33] i[02]: pstnrcv alert cr 7 cls ff[15:25:14.33] i[02]: rtp start cr 7 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 1[15:25:14.33] x[02]: h225snd callproc typ 1 cr 7 pri 8[15:25:14.34] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[15:25:14.38] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[15:25:14.38] a[02]: vp ch 0: in 0 out 74[15:25:15.57] r[00]: 02 01 50 54 08 02 80 08 07 29 05 06 03 18 0f 17 4c 06 01 81 31 37 33 31 [15:25:15.57] s[00]: 00 01 54 52 08 02 00 08 0f [15:25:15.57] i[02]: pstnrcv connresp cr 7 acc 10 ch 255[15:25:15.57] x[02]: h225snd callproc typ 7 cr 7 pri 0[15:25:15.58] r[00]: 00 01 01 56 [15:25:17.01] a[02]: vp rtcp 0: SR Rx pc 110 oc 1816 ji 158 rt -1 fl 2 cl 1[15:25:20.09] a[02]: vp rtcp 0: SR Tx pc 277 oc 5496 ji 164 rt 0 fl 0 cl 0[15:25:20.09] a[02]: vp ch 0: in 18166 out 20646[15:25:20.09] a[02]: vp rtcp 0: SR Rx pc 258 oc 4634 ji 208 rt -1 fl 0 cl 1[15:25:23.32] a[02]: vp rtcp 0: SR Tx pc 441 oc 8776 ji 176 rt 0 fl 0 cl 0[15:25:23.32] a[02]: vp ch 0: in 28966 out 32900[15:25:24.68] y[02]: h225rcv tpkt msg 5a h225cr 8006 addr 172.16.0.200 pt 800e7800[15:25:24.68] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[15:25:24.68] y[02]: h225rcv relack h225cr 8006 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:25:24.68] y[02]: h225rcv relack h225cr 8006 cau 0x10[15:25:24.68] i[02]: rtp hold cr 7 ch 1[15:25:24.68] s[00]: 00 01 56 52 08 02 00 08 45 08 02 80 90 [15:25:24.68] i[02]: h225 connection 4 terminated[15:25:24.69] r[00]: 00 01 01 58 [15:25:25.89] r[00]: 02 01 52 58 08 02 80 08 4d [15:25:25.89] s[00]: 00 01 58 54 08 02 00 08 5a [15:25:25.94] i[02]: pstnrcv terminate connection (3201) cr 7 cau 1 err 16 state 17 ch 1 rsid 1[15:25:25.94] i[02]: rtp stop cr 7 ch 1[15:25:25.94] r[00]: 00 01 01 5a [15:25:25.94] a[02]: vp ch 0: in 34096 out 38154[15:25:25.94] a[02]: vp stop ch=0

10 System maintenance and software updatePage 183CELLX 16.2Outgoing H.323 call with FastStartExample 10.7 Outgoing H.323 call with FastStart[15:04:09.12] r[00]: 02 01 46 48 08 02 22 54 05 04 03 80 90 a3 18 03 a9 83 94 6c 06 01 81 31 31 31 31 70 04 81 33 32 31 7d 02 91 81 [15:04:09.12] s[00]: 02 01 01 48 [15:04:09.12] s[00]: 00 01 48 48 08 02 a2 54 0d 18 03 a9 83 94 [15:04:09.12] i[02]: pstnrcv setup dad DF:321 oad 1111 cc 0 id 15d006[15:04:09.12] i[02]: pstnrcv get_voipcfg <DF>[15:04:09.12] i[02]: h225connect to 172.16.0.200 cr 6[15:04:09.12] x[02]: h225snd setup dad 1 cr 6[15:04:09.12] r[00]: 00 01 01 4a [15:04:09.15] y[02]: h225rcv tpkt msg d h225cr 6 addr 172.16.0.200 pt 80412800[15:04:09.15] y[02]: h225 decode rc 0, q931 msg d (11), len 32[15:04:09.15] y[02]: h225rcv msg d (11) h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:09.50] y[02]: h225rcv tpkt msg 1 h225cr 6 addr 172.16.0.200 pt 80412800[15:04:09.50] y[02]: h225 decode rc 0, q931 msg 1 (3), len 121[15:04:09.50] y[02]: h225rcv faststart <E1>[15:04:09.50] y[02]: h225rcv alert h225cr 6 FS:1(E,172.16.0.200,29000) TUNN:1 H245:0(0,0)[15:04:09.50] i[02]: rtp start cr 6 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 1[15:04:09.50] s[00]: 00 01 4a 48 08 02 a2 54 01 1e 02 80 88 [15:04:09.50] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[15:04:09.50] r[00]: 00 01 01 4c [15:04:09.53] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[15:04:09.53] a[02]: vp ch 0: in 0 out 74[15:04:11.79] y[02]: h225rcv tpkt msg 7 h225cr 6 addr 172.16.0.200 pt 80412800[15:04:11.79] y[02]: h225 decode rc 0, q931 msg 7 (2), len 79[15:04:11.79] y[02]: h225rcv connect h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:11.79] i[02]: pstnsnd connect cr 6[15:04:11.79] s[00]: 00 01 4c 48 08 02 a2 54 07 [15:04:11.80] r[00]: 02 01 48 4e 08 02 22 54 0f [15:04:11.80] s[00]: 02 01 01 4a [15:04:12.50] a[02]: vp rtcp 0: SR Rx pc 21 oc 394 ji 201 rt -1 fl 0 cl 0[15:04:16.13] a[02]: vp rtcp 0: SR Tx pc 192 oc 3236 ji 196 rt 0 fl 0 cl 0[15:04:16.13] a[02]: vp ch 0: in 14612 out 13796[15:04:17.98] y[02]: h225rcv tpkt msg 5a h225cr 6 addr 172.16.0.200 pt 80412800[15:04:17.98] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[15:04:17.98] y[02]: h225rcv relack h225cr 6 FS:0(-,0,0) TUNN:1 H245:0(0,0)[15:04:17.98] y[02]: h225rcv relack h225cr 6 cau 0x10[15:04:17.98] i[02]: rtp hold cr 6 ch 1[15:04:17.98] s[00]: 00 01 4e 4a 08 02 a2 54 45 08 02 80 90 [15:04:17.98] i[02]: h225 connection 4 terminated[15:04:17.99] r[00]: 00 01 01 50 [15:04:18.04] r[00]: 02 01 4a 50 08 02 22 54 4d 08 02 84 90 [15:04:18.04] s[00]: 00 01 50 4c 08 02 a2 54 5a [15:04:18.06] i[02]: pstnrcv terminate connection (3201) cr 6 cau 90 err 16 state 17 ch 1 rsid 1[15:04:18.06] i[02]: rtp stop cr 6 ch 1[15:04:18.06] r[00]: 00 01 01 52 [15:04:18.06] a[02]: vp ch 0: in 21288 out 20708[15:04:18.06] a[02]: vp stop ch=0

10 System maintenance and software updatePage 184CELLX 16.2Fax callExample 10.8 Fax call [16:00:40.44] i[02]: h225accept from 172.20.0.200 s 4[16:00:40.49] y[02]: h225rcv tpkt msg 5 h225cr 8007 addr 172.20.0.200 pt 0[16:00:40.49] y[02]: h225 decode rc 0, q931 msg 5 (0), len 251[16:00:40.49] y[02]: h225rcv setup voipcfg addr 172.20.0.200 rc 0 <DF> compr EABG[16:00:40.49] y[02]: h225rcv faststart <E0G0>[16:00:40.49] y[02]: h225rcv setup oad 00 00 <> <> dad 01 <123456> rad <> bc 038090a3 0101[16:00:40.49] y[02]: h225rcv setup h225cr 8007 FS:1(E,172.20.0.200,29000) TUNN:1 H245:0(0,0)[16:00:40.49] y[02]: h225rcv setup h225cr 8007 cr 14[16:00:40.49] i[02]: pstnsnd setup dad 123456 oad cr 14 s 4[16:00:40.49] s[00]: 00 01 5a 54 08 02 00 09 05 04 03 80 90 a3 18 03 a1 83 88 70 07 81 31 32 33 34 35 36 7d 02 91 81 [16:00:40.49] i[02]: pstnrcv connresp cr 14 acc 5 ch 1[16:00:40.49] x[02]: h225snd callproc typ d cr 14 pri 0[16:00:40.50] r[00]: 02 01 54 5c 08 02 80 09 0d 18 03 a9 83 88 [16:00:40.67] r[00]: 02 01 56 5c 08 02 80 09 01 [16:00:40.67] i[02]: pstnrcv alert cr 14 cls ff[16:00:40.67] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 2 fx 0 cp E txm 2[16:00:40.67] x[02]: h225snd callproc typ 1 cr 14 pri 8[16:00:40.70] a[02]: vp start(201) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[16:00:40.74] a[02]: vp rtcp 0: RR Tx pc 0 oc 0 ji -1 rt 0 fl -1 cl -1[16:00:40.74] a[02]: vp ch 0: in 0 out 74[16:00:40.90] r[00]: 02 01 58 5c 08 02 80 09 07 29 05 06 03 18 0f 3b 4c 08 01 81 31 32 33 34 35 36[16:00:40.90] s[00]: 00 01 5c 5a 08 02 00 09 0f [16:00:40.90] i[02]: pstnrcv connresp cr 14 acc 10 ch 255[16:00:40.90] x[02]: h225snd callproc typ 7 cr 14 pri 0[16:00:41.98] a[02]: vp rtcp 0: SR Rx pc 134 oc 1340 ji 195 rt -1 fl 0 cl 0[16:00:43.29] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.29] y[02]: h225 decode rc 0, q931 msg 62 (6), len 123[16:00:43.29] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.29] i[02]: h245rcv(1) cr 14 TerminalCapabilitySet peer=<EG> cfg=<EABG>[16:00:43.29] i[02]: h245snd(1) cr 14 TerminalCapabilitySetAck[16:00:43.29] i[02]: h245snd(1) cr 14 TerminalCapabilitySet <EABG>[16:00:43.51] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.51] y[02]: h225 decode rc 0, q931 msg 62 (6), len 63[16:00:43.51] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.51] i[02]: h245rcv(1) cr 14 TerminalCapabilitySetAck[16:00:43.72] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.72] y[02]: h225 decode rc 0, q931 msg 62 (6), len 74[16:00:43.72] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.72] i[02]: h245rcv(1) cr 14 RequestMode t38=1[16:00:43.72] i[02]: h245snd(1) cr 14 RequestModeAck[16:00:43.73] i[02]: h245snd(1) cr 14 CloseLogicalChannel cn=1[16:00:43.73] i[02]: h245snd(1) cr 14 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.100:29001[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 68[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 CloseLogicalChannel cn=1 (1)[16:00:43.73] i[02]: h245snd(1) cr 14 CloseLogicalChannelAck cn=1[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 92[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 OpenLogicalChannel cn=1 cpr=G sessid=1 ctrl=172.20.0.200:29001[16:00:43.73] i[02]: h245snd(1) cr 14 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.100:29000[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 64[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 CloseLogicalChannelAck cn=1[16:00:43.73] y[02]: h225rcv tpkt msg 62 h225cr 8007 addr 172.20.0.200 pt 80410800[16:00:43.73] y[02]: h225 decode rc 0, q931 msg 62 (6), len 83[16:00:43.73] y[02]: h225rcv facility h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:00:43.73] i[02]: h245rcv(1) cr 14 OpenLogicalChannelAck cn=1 sessid=1 media=172.20.0.200:29000

10 System maintenance and software updatePage 185CELLX 16.210.7.4 Remote outputThis trace option provides output for communication with the GATE Manager or NMS. To ac-tivate this option, activate the section Remote in the GATE Manager. You can choose thedepth of the trace output: Error is limited to error messages; Debug provides information;Detail provides the entire packet.Output is defined with a g, and the port number is 99.The following output shows an established GATE Manager connection:g[99]:moip: accept rc=2 ipad=<ip address> port=<port>.The following output shows the direction (In/Out) for the packet and the size.[16:00:43.73] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 3 fx 0 cp G txm 2[16:00:43.73] i[02]: rtp start cr 14 ch 1 li 1 ri 1 st 3 fx 1 cp G txm 2[16:00:43.74] a[02]: vp start2 ch=0 remote=ac1000c8:29000[16:00:43.74] a[02]: vp start(401) ch=0 local=29000 remote=ac1000c8:29000 agg=0 pcm=0[16:00:47.70] a[02]: vp rtcp 0: SR Tx pc 13 oc 352 ji 132 rt 0 fl 0 cl 0[16:00:53.63] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:00:59.14] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:02.12] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:07.16] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:11.82] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:18.06] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:21.15] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:26.10] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:28.89] a[02]: vp rtcp 0: RR Tx pc 13 oc 352 ji -1 rt 0 fl -1 cl -1[16:01:33.14] y[02]: h225rcv tpkt msg 5a h225cr 8007 addr 172.20.0.200 pt 80410800[16:01:33.14] y[02]: h225 decode rc 0, q931 msg 5a (5), len 33[16:01:33.14] y[02]: h225rcv relack h225cr 8007 FS:0(-,0,0) TUNN:1 H245:0(0,0)[16:01:33.14] y[02]: h225rcv relack h225cr 8007 cau 0x10[16:01:33.14] i[02]: rtp hold cr 14 ch 1[16:01:33.15] s[00]: 00 01 5e 5a 08 02 00 09 45 08 02 80 90 [16:01:33.15] i[02]: h225 connection 4 terminated[16:01:33.19] r[00]: 02 01 5a 60 08 02 80 09 4d [16:01:33.19] s[00]: 00 01 60 5c 08 02 00 09 5a [16:01:33.19] i[02]: pstnrcv terminate connection (3201) cr 14 cau 1 err 16 state 17 ch 1 rsid 1[16:01:33.19] i[02]: rtp stop cr 14 ch 1[16:01:33.23] a[02]: vp ch 0: in 85542 out 4346[16:01:33.23] a[02]: vp stop ch=0Example 10.8 Fax call (continued)Table 10.51 Remote output Trace Output Description<ip address> Remote system’s IP address with GATE Manager.<port> Origination port for the GATE Manager connec-tion.

10 System maintenance and software updatePage 186CELLX 16.2g[99]:moip: <direction> <length>.All other trace output appears in detail mode in ASCII and are also translated.10.7.5 SMTP trace outputThis trace option provides output for communication with the mail server that occurs whenstatus information or files are sent, or in the other direction, which e-mails are received andconverted to SMS or USSD.To activate this option, activate the section Mail in the GATE Manager. You can choose thedepth of the trace output: Error is limited to error messages; Debug provides information;Detail provides the entire packet.Output is defined with a m, and the port number is 99.Sending files or status informationHere is the global message output syntax:m[99]:mail: sendmail (<length>)The detailed message output looks like this:m[99]:mail: sendmail: <Faccount> <ip address> <Taccount> <domain> <sub-ject> <content>.Table 10.52 Remote output Trace Output Description<direction> recv Packets received from the re-mote systemsend Packets sent to the remote sys-temwrite Output for communication with the internal remote interfaceread Output for communication from the internal remote inter-face<length> Data length in bytes.Table 10.53 SMTP output: sending files or status info Trace Output Description<length> Data length in bytes.Table 10.54 SMTP output: sending fles or status info Trace Output Description<Faccount> Sender’s e-mail account (cdr, alarm, file, and so on).<ip address> SMTP server’s IP address.

10 System maintenance and software updatePage 187CELLX 16.2All other trace output appears in detail mode in ASCII and are also translated.Receiving e-mail messages and sending them as SMS or USSDThe following output displays communication of an incoming SMTP connection:m[99]:mail: accept: ipad=<ip address> port=<port>The following output displays which packets are sent to the SMTP peer:m[99]:mail: mysend <<content>>All other trace output appears in detail mode in ASCII and are also translated.The following output displays which packets are received from the SMTP peer:m[99]:mail: recv (<length>)All other trace output appears in detail mode in ASCII and are also translated.The following output shows that the SMTP connection is being closed:m[99]:mail: terminate_session<Taccount> Recipient’s e-mail account.<domain> Recipient’s domain.<subject> Content of the subject field; serial number of the sender system.<content> Content of the message’s body.Table 10.54 SMTP output: sending fles or status info (continued)Trace Output DescriptionTable 10.55 SMTP output: receiving e-mail and sending as SMS or USSD Trace Output Description<ip address> The SMTP peer system’s IP address.<port> The SMTP peer system’s origination port.Table 10.56 SMTP output: receiving e-mail and sending as SMS or USSD Trace Output Description<content> Content of the transmitted packet.Table 10.57 SMTP Output: receiving e-mail and sending as SMS or USSD Trace Output Description<length> Data length in bytes.

10 System maintenance and software updatePage 188CELLX 16.2The mail module now converts the e-mail message to the internal format and then sent asSMS or USSD. Bulk mail (several recipient entries for the same e-mail) appear as individualmessages:m[99]:mail: newMail2Host r=<Taccount> f=<Faccount> s=<subject> d=<content> The following output appears when the message has been successfully sent:m[99]:mail: rcvmail <Faccount> -> <Taccount>, doneThis is converted in the confirmation message, with the subject sent. The output in the sub-sequent communication with the mail server are identical to those described above inChapter Sending files or status information.The following output appears when errors occur during transmission of the SMS or USSDmessage:Message transmission was faulty and will be repeated:m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed, will retry(<num>)Retried message transmission was also faulty, and an e-mail will be generated:m[99]:mail: rcvmail <Faccount> -> <Taccount>, failed <num> timesThe output in the subsequent communication with the mail server are identical to those de-scribed above in Chapter Sending files or status information. Receiving SMS or USSD and sending as e-mailThe following output shows the internal format when an SMS or USSD message is sent to themail module. This output is generated when transmission of the SMS or USSD message wasnot possible:m[99]:mail: DATA_IND (<length>).All other trace output appears in detail mode in ASCII and are also translated. The output inthe subsequent communication with the mail server are identical to those described above inChapter Sending files or status information.Table 10.58 SMTP output: receiving e-mail and sending as SMS or USSD Trace Output Description<Faccount> One entry from the sender’s To field.<Taccount> Content of the From field.<subject> Content of the subject field; usually not used.<content> Content of the message’s body; is sent as SMS or USSD.Table 10.59 SMTP output: transmission error Trace Output Description<num> Current number of retries.

10 System maintenance and software updatePage 189CELLX 16.210.7.6 Number portability trace outputThis trace option provides output for the communication with the iMNP database. To activatethis option, activate the section Number Portability in the GATE Manager. Output is definedwith an n, and the port number is 99.The following output appears when the system sets up a TCP session with the iMNP is beingset up:n[99]:np: connecting to <ip addr>.The following output shows that the connection has been established:n[99]:np: connect to <ip addr> ok.The following output shows that the connection attempt failed:n[99]:np: connect to <ip addr> failed.The following output shows a keep alive packet from the iMNP to keep the TCP session open:n[99]:np: recv <>.Response to a number portability request that results in the call’s routing:n[99]:np: recv <N<num>>.10.7.7 DTMF tone trace outputOutput about the setup of connections with the DTMF module and DTMF tone detection aredebugged. The output differentiates between the groups err and inf. Output is definedwith a d, and the port number is that of the virtual DTMF controller:The following output shows incoming call setup to the DTMF module:Table 10.60 Number portability output: connection with iMNP Trace Output Description<ip address> The iMNP system’s IP address.Table 10.61 Number portability output: response Trace Output Description<num> Ported or unported number provided by the da-tabase.

10 System maintenance and software updatePage 190CELLX 16.2d[<ctrl>]: dtmf: msg <call state>, unknown id <id>, from 14.The following output shows transmitted signaling messages depending on the call state:d[<ctrl>]: dtmf <message type> <id> <call state> 0.The following output shows that the media channel has been designated for DTMF tone de-tection:d[<ctrl>]: dtmf send_alloc <b_chan id_unset> <ctrl>/<b chan>.The following output shows the status for the media channel will is/was used for DTMF tonerecognission:Table 10.62 DTMF output: incoming call setup Trace Output Description<ctrl> The virual controller’s running number.<call state> 3101 Incoming setup3201 Disconnect request<id> Call identification number.Table 10.63 DTMF output: signaling messages Trace Output Description<message type> Send_d_connect For setup acknowledge and connect.send_alert_ind For alert.send_disconnect For disconnect<id> Call identification number.<call state> 3110 Incoming setup3102 Disconnect request3804 Alert3202 Disconnect confirmationTable 10.64 DTMF output: media channel designation Trace Output Description<b chan> Internal media channel used.<b_chan id_unset> Media channel identification (in unset state).

10 System maintenance and software updatePage 191CELLX 16.2d[<ctrl>]: dtmf: msg <msg>, id <b_chan id>, from 1, id <id>/<b_chanid_unset>.The following output shows the output for negotiated DTMF tones:d[<ctrl>]: dtmf send_info_ind <id> <<dtmf tone>>.Table 10.65 DTMF output: media channel designation Trace Output Description<msg> 502 Media channel confirmation102 Connect confirmation602 Media channel free confirma-tion

11 Feature packagesPage 193CELLX 16.2The feature packages are modular expansion applications that provide services in addition tothose offered with the standard software. Feature packages can be activated separately or incombination with one another, so that you can design your system according to your ownneeds.The following feature packages are available:Two Stage Dialing/Callback Services (please see Chapter 11.2 on page 194)Least Cost Routing (please see Chapter 11.3 on page 200)Online Traffic Monitor (please see Chapter 11.4 on page 206)Ported Number Screening (please see Chapter 11.5 on page 213)Call recording (please see Chapter 11.6 on page 215)11.1 Activating the licenseEach feature package requires a license. Once you have ordered a feature package, you canactivate the license:The /boot/ directory of each system contains a file called license.key, which contains infor-mation on the system’s ID, the included components, which feature packages are active andthe license number:You will receive a new license.key file any time you order a new license package. Simply savethe new file, overwriting the old file, and restart the system. Example 11.1 Activating the license[IDENTIFICATION]SYSTEM: TELES.iGATESERNO: VT810011AUTOR: create Wed Sep 09 15:01:09 2006[COMPONENTS]...CARD99:11 d1 S0 PB900034...[FEATURES]PRI:MaxGSM:MaxIP:MaxVoIP:MaxSIM manager: OnDDI and call back: Offleast cost routing: Onstatistics and CDR: OnSMS gateway: Onported number screening: Offroaming: Off[SIGNATURE]00000000000license0number00000000000Deleting or making changes in the license.key file will delete any feature package licenses, causing the system to revert to the standard configuration! ii

11 Feature packagesPage 194CELLX 16.211.2 Two stage dialing/callback server functionalityThis package contains money-saving features that expand the functionality of your to includeDTMF services (two stage dialing) and callback capability. It is particularly useful for companieswith employees who travel often, because it eliminates expensive roaming fees.In a two stage dialing scenario, the caller dials a number which the connects with the inte-grated DTMF platform. He then enters the destination number via DTMF. The establishes theconnection to the destination number. Callback takes place, when the initial call is released and the calling party is called back in asecond call as a response.Depending on your , various intelligent solutions as a call server are possible. The most impor-tant scenarios and properties are described here. The scenarios can also be combined to suityour needs.Announcements Two stage dialing with DTMFCallback with DTMF and OAD as callback numberCallback with DTMF and preconfigured callback numberCallback to OAD with predefined destination numberCallback with PIN and preconfigured callback numberTo indicate that the number transmitted using DTMF tones is complete, the caller can pressthe # key. Otherwise, there is a default timer set to 5 seconds, after which DTMF transmissionwill automatically end.To correct a wrong destination number, the caller can press the * key. The DTMF announce-ment is replayed and the destination number can be entered again.Activating DTMF tone recognitionThe can recognize DTMF tones and use them to initiate calls. In the pabx.cfg, enter a virtualDTMF controller, as described in Table 5.14. The corresponding Subscriber entry contains theoptions:TRANSPARENT ROUTER CHMAX[5]The 5 refers to the maximum number of simultaneous channels used for DTMF recognition.The must be restarted to activate this configuration.CDR entries for calls routed as callback with DTMF include the connection times for the A and B parties. The times are separated by a slash (/). If no connection is established to the B party, an entry recording the A party’s connection time is generated in the failed.log file.iiExample 11.2 Activating DTMF tone recognition...Controller20 = 41 DTMF...Subscriber20 = TRANSPARENT ROUTER CHMAX[5]...

11 Feature packagesPage 195CELLX 16.211.2.1 AnnouncementsAn announcement can be played immediately after the connection has been established. Theannouncement’s file format must be G.711. A converter tool to convert wave files to theG.711 format is available from TELES free of charge. The announcement can be defined inthe virtual DTMF controller’s Subscriber line using the following entry in the pabx.cfg file:DTMF[<sec>,/<dir>/<file>]<sec> refers to the maximum number of seconds after which the connection to the DTMFcontroller is teared down. Please enter a time that is longer than the announcement time. Theentry <dir> refers to the directory in which the announcement file is saved. The directoryname can be boot or data. The file extension must be 711.The Subscriber line can be extended to contain up to 26 additional announcement files:DTMF[<sec>,/<dir>/<defaultfile>,/<dir>/<file_a>,/<dir>/<file_b>,...,/<dir>/<file_z>]A mapping needs to be added to the route.cfg file for every announcement to map to theport that is necessary for recognizing DTMF tones:MapAll<number>=<DTMFport>DTMF (for the default announcement file)MapAll<number>=<DTMFport>DTMFa (for file_a)...MapAll<number>=<DTMFport>DTMFz (for file_z)To stop the announcement after the entry of the first digit, a [ needs to be added behindDTMF to the respective MapAll parameter:MapAll<number>=<DTMFport>DTMF[In this example, a maximum of 5 channels can recognize DTMF tones and change them intodialing data. The default announcement is named DTMF1.711 and must be available in theboot directory. There is one additional announcement file named DTMF2.711 which mustalso be available in the boot directory. Users calling in from GSM hear the default announce-ment. After entry of the first digit, the annoucement stops. Calls coming in from analogsources trigger the announcement a stored in file_a.11.2.2 Two stage dialing with DTMFThe user dials a number in the system that is connected with the virtual DTMF controller. Hethen enters the number he wants to be connected to.Make the following entries in the route.cfg to connect a call directly:MapAll<number>=<DTMFport>DTMFMaps the calls to the DTMF port.Example 11.3 Announcements configuration in the pabx.cfgController20 = 41 DTMFSubscriber20 = TRANSPARENT ROUTER DTMF[30,/boot/DTMF1.711,/boot/DTMF2.711] CHMAX[5]Example 11.4 Announcements configuration in the route.cfgRestrict20 = IN1Restrict10 = IN2MapAllIN1 = 41DTMF[MapAllIN2 = 41DTMFa[

11 Feature packagesPage 196CELLX 16.2MapAllDLA=<port>Sends all digits that have been entered as DTMF to the specified port. To prevent abuse, thefollowing entry can be made to configure a PIN before the actual call number:MapAllDLA<pin>=<port>In addition, the mapping to the DTMF port can be extended by the capital letters C to Z tosend the digits to different ports:MapAll<number>=<DTMFport>DTMFCMapAll<number>=<DTMFport>DTMFD... MapAll<number>=<DTMFport>DTMFZmust be combined with:MapAllDLC=<port>MapAllDLD=<port>...MapAllDLZ=<port>In the following example, all calls coming from GSM are connected to the virtual DTMF con-troller and the call that comes in as DTMF tones is directed to port 9. Calls to the number12345 are connected to the virtual DTMF controller and are directed to port 10.In the folllowing example, two announcement files are listed in the pabx.cfg. All calls com-ing from GSM are connected to the virtual DTMF controller and the default announcement(DTMF1.711) is played. The call that comes in as DTMF tones is directed to port 9. Calls to thenumber 12345 are connected to the virtual DTMF controller and the DTMF2.711 announce-ment is played. The call that comes in as DTMF tones is directed to port 10.Example 11.5 Two stage dialing with DTMF 1Restrict20=INMapAllIN=41DTMFMapAllDLA=9MapAll12345=41DTMFCMapAllDLC=10Example 11.6 Two stage dialing with DTMF 1 (pabx.cfg)Controller20 = 41 DTMFSubscriber20 = TRANSPARENT ROUTER DTMF[30,/boot/DTMF1.711,/boot/DTMF2.711] CHMAX[5]Example 11.7 Two stage dialing with DTMF 1 (route.cfg)Restrict20=INMapAllIN=41DTMFMapAllDLA=9MapAll12345=41DTMFaCMapAllDLC=10

11 Feature packagesPage 197CELLX 16.211.2.3 Callback with DTMF and OAD as callback numberThe user calls a number to trigger callback to his calling number (OAD). After the alert tone,the system or the user hangs up and the user is called back. When he takes the call, he isrequested by announcement to enter the destination number using DTMF tones. The connec-tion to the destination number is then established.The following entries in route.cfg will initiate callback to the calling party’s number:MapAll<number>=CALLBThis entry contains the number that needs to be called to trigger callback.MapCallbackAlert=<sec>If this optional parameter is configured, the will release the trigger call after the given numberof seconds. The default value is 180. If you enter the value 1, no alert tone is sent. For all otherentries an alert tone is sent. The range of possible values is between 1 and 255.MapCallbackDelay=<sec>If MapCallbackAlert=<sec> is configured, MapCallbackDelay=<sec> is needed to definethe time between the release of the trigger call and the call back. The parameter is used toset up the call back. A callback delay of 2 to 5 seconds is recommended.MapCallbackRejCause=<cause value>If this optional parameter is configured, the trigger call to the gateway is rejected with thehere entered cause value. The default value is 16 (Normal call clearing). The values 1 - 127 arepossible. This parameter is not available for mobile ports.MapAllCB=<port>Calls back the calling party’s number via the defined port.MapAllDTMF=<DTMFport>DTMFMaps to the port that is needed for recognizing DTMF tones.MapAllDLA=<port>Sends all digits that have been entered as DTMF to the specified port.The letter “B” in CALLB can be replaced by any capital letter from C to Z to allow for differentroutings. Correspondingly, “B” in MapAllCB and “A” in MapAllDLA need to be replaced bya matching capital letter C to Z:MapAll<number>=CALLCMapAll<number>=CALLD...MapAll<number>=CALLZcorresponds with:MapAllCC=<port>MapAllCD=<port>...MapAllCZ=<port>corresponds with:MapAllDLC=<port>MapAllDLD=<port>...MapAllDLZ=<port>MapCallbackMaxDuration=<sec>This optional parameter defines the length of time that the system tries to call back the user.The entered value can be between 1 and 180. If the time limit has been exceeded, the systemterminates the call.CallbackOAD=<OAD>Configure this optional parameter in the [System] section of the pabx.cfg file to display thehere defined OAD when the gateway calls back the user. Not possible for mobile ports.

11 Feature packagesPage 198CELLX 16.2In this scenario, there is no need to adjust the MapAllDTMF=<DTMFport>DTMF command.In this example, the number 123 is called to trigger a callback. After 3 seconds the releasesthe call. The calling party’s number (OAD) is called back via port 9. The user is requested toenter the destination number as DTMF. The digits that come in as DTMF are sent to port 9.This example is similar to the above one except that the port for the destination call is nowport 10. The capital letter “C” is used in the mappings to allow for this additional routing.11.2.4 Callback with DTMF and preconfigured callback numberThis feature is especially useful when the calling party’s number is not transmitted. The usercalls a predefined number that is mapped to a defined callback number. An alerting takesplace. The user hangs up and is called back at the defined callback number. After the userhas accepted the call, he must enter the destination number via DTMF. The connection is setup when he finishes dialing.Make the following entries in route.cfg to initiate callback to a fixed number:MapAll<number>=CALL<callback number>MapAllDTMF=<DTMFport>DTMFMapAllDLA=<port>You need to activate digit collection if the call goes to the mobile network or VoIP (using SIP)iiExample 11.8 Callback with DTMF and OAD as callback number 1MapAll123=CALLBMapCallbackAlert=3MapCallbackDelay=5MapAllCB=9MapAllDTMF=41DTMFMapAllDLA=9MapCallbackMaxDuration=180Example 11.9 Callback with DTMF and OAD as callback number 2MapAll456=CALLCMapCallbackAlert=3MapCallbackDelay=5MapAllCC=9MapAllDTMF=41DTMFMapAllDLC=10MapCallbackMaxDuration=60

11 Feature packagesPage 199CELLX 16.2In the following example, calls to the number 123 are connected with the number 03012345.The number that comes in as DTMF is directed to port 9.11.2.5 Callback to OAD with predefined destination numberThe user calls a predefined number in the system. An alerting occurs. The user hangs up andis called back on his calling party number (OAD). After the user accepts the call, he is connect-ed to a fixed, preconfigured number (e.g. operator or corporate central office).Make the following entries in route.cfg:MapAll<number>=CALLBMapAllCB=<port>MapAllDTMF=<port><destination number>Different routings are possible by using the capital letters “C” to “Z”. In the following example, the caller dials 123456 and his OAD is called back through port 9.He is then connected with the operator’s number 0 through port 10.In the following example, the caller dials 987654 and his OAD is called back through port 9.He is then connected to the destination number 03011111 through port 9.11.2.6 Callback with PIN and preconfigured callback numberThe user dials a number in the system that is connected to the DTMF platform. He then entersa predefined PIN that maps him to a predefined fixed number that is to be called back. Hethen hangs up. After he takes the callback, he can enter the destination number using DTMFtones. Make the following entries in route.cfg:MapAll<number>=<DTMFport>DTMFMapAllDLA<pin>=CALL<port><callback number>MapAllDTMF=<DTMFport>DTMFMapAllDLA=<port>Example 11.10 Callback with DTMF and preconfigured callback numberMapAll123=CALL903012345MapAllDTMF=41DTMFMAPAllDLA=9Example 11.11 Callback to OAD with predefined destination number 1MAPAll123456=CALLBMapAllCB=9MapAllDTMF=100Example 11.12 Callback to OAD with predefined destination number 2MAPAll987654=CALLCMapAllCC=9MapAllDTMFC=903011111

11 Feature packagesPage 200CELLX 16.2The number 123456 is dialed and the PIN 123# is entered. The call is then connected to thepre-configured callback number 004930123456 through port 9. After connect, the destina-tion number is entered using DTMF and transmitted through port 9.The number 987654 is dialed and the PIN 456# is entered. The call is then connected to thepre-configured callback number 004930987654 through port 9. The capital letter “C” isused in the mappings to allow for this additional callback number. After connect, the desti-nation number is entered using DTMF and transmitted through port 9.11.3 Least cost routings are connected between the customer’s private branch exchange (PBX) and the public tele-phone network (ISDN) and/or VoIP. The customer saves connection charges and can effort-lessly and automatically connect to the corporate network as needed using one of six routingmethods:Carrier selectionDedicated linesDirect line access with subaddressingDirect line access with DTMFCallback with subaddressingCallback with DTMFThis manual contains information only on carrier selection. If you would like to configure anyother variation, please contact TELES.Calls are routed transparently for the PBX and its users. s can generate charges and route callsusing alternate settings in case of network failures. The provider can access the system viaISDN for routine maintenance and monitoring.The following additional services are supported by this feature package:Generation of chargesTime-controlled configurationAlternative routingExample 11.13 Callback with PIN and preconfigured callback number 1MAPAll123456=41DTMFMapAllDLA123=CALL9004930123456MapAllDTMF=41DTMFMapAllDLA=9Example 11.14 Callback with PIN and preconfigured callback number 2MAPAll987654=41DTMFCMapAllDLC456=CALL9004930987654MapAllDTMF=41DTMFMapAllDLA=9The user must enter a # following the PIN. Otherwise the callback to the predefined number will not take place.ii

11 Feature packagesPage 202CELLX 16.2MapAll<placeholder>=<alt port><num>11.3.3 Charge modelss can either generate charge information or transmit received charges from the public or cor-porate networks to the attached PBX. Charge simulation is achieved using variables, whichensure a great degree of flexibility for the implementation of many different charge modelsincluding:Charge units per time unitFlat rate (initial charge without time interval)Initial charge plus time intervalInitial charge plus time interval after delayTime interval and/or flat rate plus received chargesReceived charges only or no charge informationInitial toll-free period with retroactive charge generation afterwardsPrice-per-minute (with whole second accuracy)In this chapter, unit means that charge information is transmitted as a whole number value,and currency means that the charge information is sent as a currency amount (e.g. EUR3.45). The charge impulse generation options can be set for each mapping by adding charge-specific arguments to the MapAll commands, as shown below. The use of each variable is ex-plained in Table 11.1.MapAllsrc=dst time start/wait andMapCallBackOutprovsrc=dst mode time start/wait.To generate charge impulses from the first second of the call, the following parameter needsto be configured in the [System] section of the pabx.cfg file:InitialCharge=OnExample 11.16 Least cost routing 2MapAll01555=2621201555Redirect32621201555=AMapAllA=901555Table 11.1 Charge variables Variable Purposetime Determines the length of each time interval (how long each unit lasts). The value is entered in seconds and hundredths or thousandths of a second (the maximum value accepted is 655.35 seconds, 65.535 if thousandths are entered). If time is set to zero or not present no charges are generated. External charge informa-tion is passed through if received.start Sets the initial unit level. Enter a value between 0 and 127 whole units. If you want to use a flat rate, set the desired number of units here and set the wait to 255 to turn off the time interval.wait Determines the delay after which charge generation begins. Once this time has elapsed, charge impulses are sent at the interval determined by time. Enter a value between 0 and 254 seconds. 255 deactivates the charge pulse. In this case, the time variable is ignored.

$11 Feature packagesPage 203CELLX 16.2External charges can be added to the generated charges by adding 128 to the start value.(The value range for the initial unit level is still set from 0 to 127). The maximum supportednumber of units per connection is 32767 units.Additional adjustments may be made to allow for the implementation of new charge models.When charge information is sent as Currency hervorheben, values can be expressed inthousandths for greater precision in charge calculation.For the internal Layer 3 protocols, charges can be specified to the third decimal place(thousandth) using the /Value option (Example: /Value:1.056). In this manner, chargescan be generated for units of currency requiring accuracy to the third decimal place orfor fractions such as tenths of a cent. This allows for greater flexibility in thetransmission of charges to terminal devices. In order to make use of this option,connected devices must support “AOC-D Currency”. In the current version, this optionis only available for the DSS1 protocol.A multiplication factor can be specified for received or generated charges.During the charge generation process, each charge unit is multiplied by a preset factor.This factor appears in the mapping entry after the time and start/wait variables(MapAllsrc=dst time start/wait*factor).Each unit, for example, can be converted to 12 cents. The following example illustratesthe use of this feature:In the following example, all received charge units are multiplied by 12 and passed on. If AOC-Currency is set on the internal port, each unit appears as 12 cents.The multiplication factor is also used to implement two new charge models:If the factor value exceeds 128, this indicates the use of an initial toll-free phasefollowed by retroactive charge generation.If the multiplication factor is set to 255, a “minute price” is used in place of the timevariable.These charge models are explained under Retroactive charge generation after initial toll-freeperiod.11.3.4 Generating charges with the To generate charges for the attached PBX, add the charge variables described in Table 11.1to the MapAll commands according to the requirements of the corporate network environ-ment.In the following mapping example, time=1.65, start=131, wait=0. Three initial tariff units(131-128) are transmitted upon connection and a new unit is generated every 1.65 secondsand transmitted the next full second. Charges received from the public network for the con-nection to the corporate network dial-in node are added and transmitted (because 128 hasbeen added to the start variable’s value).Example 11.17 Charging pulse example...MapAll1=91 1 128/255*12...Example 11.18 Generating charges with the 1...MapAll0172=9123450172 1.65 131/0...$