MICROTRONIX Access 1000, Access 4000 Quick Start Manual

Download

Microtronix

Access 1000 and 4000

CDR Collection Manager

Quick Start Guide 0.9.5

4056 Meadowbrook Drive, Unit 126

London ON N6L 1E3

CANADA

www.microtronix.com

+519-690-0091

Microtronix Access - CDR Collection Manager

Table of Contents

1 CDR Collection Manager.................................................................................................................... 5

1.1 Overview....................................................................................................................................... 5

1.2 Direct Connection to Switches...................................................................................................... 5

1.2.1 X.25.......................................................................................................................................................5

1.2.2 Async/Serial..........................................................................................................................................6

1.3 Network Connection to Switches................................................................................................... 6

1.3.1 Legacy X.25 Network............................................................................................................................6

1.3.2 X.25 Over TCP (XOT) Network............................................................................................................6

1.3.3 Remote X.25/TCP Gateway Network....................................................................................................7

1.4 Collection Protocols...................................................................................................................... 7

1.4.1 AMATPS / BX.25.................................................................................................................................8

1.4.2 EADAS..................................................................................................................................................8

1.4.3 XFER.....................................................................................................................................................8

1.4.4 MTP.......................................................................................................................................................8

1.4.5 BUFFER................................................................................................................................................8

1.4.6 SoftSwitch – FTP, SCP, SFTP / IP........................................................................................................8

1.4.7 FTAM....................................................................................................................................................8

1.5 File Formats.................................................................................................................................. 8

1.5.1 AMATPS...............................................................................................................................................8

1.5.2 AMATPS +fileHeader...........................................................................................................................9

1.5.3 Martin Group.........................................................................................................................................9

1.5.4 AMA......................................................................................................................................................9

1.5.5 BAF.......................................................................................................................................................9

1.5.6 XFER fixed block..................................................................................................................................9

1.5.7 XFER variable block.............................................................................................................................9

1.5.8 EMI.......................................................................................................................................................9

1.6 File Forwarding Protocols.............................................................................................................. 9

1.6.1 FTP........................................................................................................................................................9

1.6.2 SFTP......................................................................................................................................................9

1.6.3 SCP........................................................................................................................................................9

1.7 Poll Scheduling...........................................................................................................................10

1.8 Configuration and Management Interfaces.................................................................................10

1.9 Internal X.25-TCP/IP Gateway.................................................................................................... 10

1.10 Internal Serial/TCP Terminal Server..........................................................................................10

1.11 X.25 Interface............................................................................................................................ 10

1.12 Serial Interface.......................................................................................................................... 10

1.13 Ethernet Interface...................................................................................................................... 11

1.14 USB-mounted Storage Device..................................................................................................11

1.14.1 GZIP Compression............................................................................................................................11

1.14.2 GnuPG Encryption & Compression...................................................................................................11

2 Quick Start Guide............................................................................................................................. 12

2.1 Package Check List....................................................................................................................12

2.2 Installation................................................................................................................................... 12

2.3 Console Port............................................................................................................................... 12

2.3.1 U-Boot Command Access...................................................................................................................12

2.3.2 Setting Default IP Parameters..............................................................................................................12

2.3.3 Emergency IP Address Recovery........................................................................................................13

2.3.4 System Firmware Updates...................................................................................................................13

www.microtronix.com 2

Microtronix Access - CDR Collection Manager

2.4 Configuration Web Interface........................................................................................................ 14

2.5 IP Network Configuration............................................................................................................14

2.5.1 Verifying IP network...........................................................................................................................14

2.6 Date and Time Configuration....................................................................................................... 15

2.7 CDR Collection Manager Configuration......................................................................................16

2.7.1 Network Element Name.......................................................................................................................16

2.7.2 Polling Protocol...................................................................................................................................16

2.7.3 Remote Switch Interface......................................................................................................................17

2.7.3.1 AMATPS Protocol Configuration...............................................................................................17

2.7.3.2 BUFFER Protocol Configuration.................................................................................................19

2.7.3.3 EADAS Protocol Configuration..................................................................................................20

2.7.3.4 FTAM Protocol Configuration.....................................................................................................21

2.7.3.5 MTP Protocol Configuration.......................................................................................................24

2.7.3.6 SoftSwitch Protocol Configuration..............................................................................................27

2.7.3.7 XFER Protocol Configuration.....................................................................................................29

2.7.4 X.25/TCP Gateway..............................................................................................................................31

2.7.5 FTAM Local Collector Interface (Common).......................................................................................32

2.7.6 FTAM Subnets Configuration.............................................................................................................33

2.7.7 Local Collector Interface.....................................................................................................................34

2.7.8 File Forwarding Service.......................................................................................................................35

2.7.9 File Conversion and Distribution.........................................................................................................37

2.7.10 Redundancy.......................................................................................................................................38

2.7.11 Poll Schedule.....................................................................................................................................39

2.8 X.25 WAN Port Configuration...................................................................................................... 40

2.8.1 Layer 1 – Physical...............................................................................................................................40

2.8.2 Layer 2 – Data Link.............................................................................................................................40

2.8.3 Layer 3 – Packet..................................................................................................................................41

2.9 Verifying X.25 Interface............................................................................................................... 41

2.9.1 Layer 3 – Packet..................................................................................................................................41

2.9.2 Layer 2 – Data Link.............................................................................................................................41

2.9.3 Layer 1 – Physical...............................................................................................................................42

2.10 TCP to X.25 Routing Configuration........................................................................................... 43

2.10.1 Identify inbound TCP/IP connection.................................................................................................43

2.10.2 Specify Conversion or Encapsulation Method...................................................................................43

2.10.3 Generate outbound X.25 connection..................................................................................................43

2.11 X.25 to TCP Routing Configuration........................................................................................... 45

2.11.1 Identify inbound X.25 connection......................................................................................................45

2.11.2 Generate outbound TCP/IP connection..............................................................................................45

2.11.3 Specify Conversion or Encapsulation Method...................................................................................45

2.12 Test Poll.................................................................................................................................... 46

3 Advanced Configurations................................................................................................................ 47

3.1 X.25 Link backup......................................................................................................................... 47

3.2 Second X.25 Collection Interface................................................................................................ 47

3.3 Multiple Collectors on a Single X.25 Interface............................................................................. 48

3.4 Separate Application on Second Interface of the Access 4000...................................................48

3.4.1 X.25 – TCP Conversion.......................................................................................................................49

3.4.2 X.25 Over TCP (XOT)........................................................................................................................49

3.4.3 Serial Terminal Server.........................................................................................................................49

4 WAN Cables...................................................................................................................................... 51

www.microtronix.com 3

Microtronix Access - CDR Collection Manager

4.1 Connecting to a DCE..................................................................................................................51

4.2 Connecting to a DTE................................................................................................................... 51

5 Contact Microtronix.......................................................................................................................... 52

www.microtronix.com 4

Microtronix Access - CDR Collection Manager

1 CDR Collection Manager

1.1 Overview

The Microtronix Access – CDR Collection Manager (CCM) polls legacy Central Office (CO) voice switches or soft switches for files containing CDR, AMA, EADAS, SMDR, and other call/traffic data records over X.25, serial, or IP interface(s) using the polling or file transfer protocol supported by the switch. The collected files are stored and may be converted to a format suitable for the downstream server. The stored files are pushed to or pulled from a mediation, billing, or other application server over an IP network using secure or non-secure file transfer protocols.

In addition, the built-in X.25/TCP Gateway and Serial/TCP Terminal Server allow simultaneous connections to the switch from operations and other management client applications like command line interfaces.

1.2 Direct Connection to Switches

1.2.1 X.25

The CCM can replace any X.25 or dial-up networking by connecting directly to a switch's X.25 interface and provides local storage for collected files. This increases the speed and reliability of the collection

www.microtronix.com 5

Microtronix Access - CDR Collection Manager

process, and reduces the exposure to network outages.

The Access 4000 has 2 X.25 interfaces that can be configured for collection of 1 or 2 switches. The Access 1000 has a single X.25 interface. Each X.25 interface can support multiple collector configurations, for example, call record data on one collector configuration, and traffic data on another collector configuration.

1.2.2 Async/Serial

The CCM can replace any serial dial-up networking by connecting directly to a switch's async/serial interface for collection of data or for management clients.

1.3 Network Connection to Switches

The CCM supports multiple switches connected through X.25, and/or IP network connections.

1.3.1 Legacy X.25 Network

The CCM can be configured to support multiple switches through a single X.25 interface connected to an X.25 network. Each collector configuration uses the same X.25 interface, but with unique X.25 destination addresses.

1.3.2 X.25 Over TCP (XOT) Network

Similar to the legacy X.25 network, a virtual X.25 network that uses an XOT/IP infrastructure with XOT routers or gateways connected to the switches is also supported. The CCM can connect to an X.25 end-point or to the XOT/IP network directly. The Microtronix Access X.25/TCP Gateway is an example of an XOT Gateway.

www.microtronix.com 6

1.3.3 Remote X.25/TCP Gateway Network

Microtronix Access - CDR Collection Manager

TCP/IP to remote X.25/TCP Gateways connected to the switches, using RFC1006, RBP, AEPN, etc encapsulation.

1.4 Collection Protocols

Collection protocols are used for retrieving data (polling) from switches for storage in local files. Some protocols also allow the switch to push the files.

Supported switch polling or file transfer protocols are:

www.microtronix.com 7

Microtronix Access - CDR Collection Manager

1.4.1 AMATPS / BX.25

Automatic Message Accounting Teleprocessing System as per GR-385-CORE (also known as BX.25) is used for collection of AMA records over an X.25 interface. Commonly used on Siemens EWSD and Lucent 5ESS switches.

1.4.2 EADAS

Engineering and Administrative Data Acquisition System is used for collection of various traffic and other data at specific timed intervals over an X.25 interface.

1.4.3 XFER

Nortel XFERPRO (Data Transferral Application Protocol) is used for collection of AMA, SMDR, and other types of data over an X.25 interface. Used on various Nortel switches like the DMS100 model.

1.4.4 MTP

Ericsson Message Transfer Protocol is used for collection of CDR and other types of data over an X.25 interface. The collector can be configured as a client to initiate polling sessions using Server File Input (SFI) mode, or act as a server to wait for the switch to initiate a push using Server File Output (SFO) mode.

It can also be configured for Command Line Interface (CLI) that allows a standard terminal user to connect to the AMTP (Alphanumeric terminal over Ericsson MTP) interface of the AXE.

1.4.5 BUFFER

Data buffering of byte-stream ASCII data over an X.25 or serial interface from the switch. This allows the collector to gather “continuous” raw data from the switch into files for forwarding. This method has no protocol handshake. The collector can initiate or receive a connection to/from the switch and runs continuously as daemon.

1.4.6 SoftSwitch – FTP, SCP, SFTP / IP

The SoftSwitch protocol uses FTP, SCP, or SFTP to pull files from IP-based soft switches like Metaswitch and Cisco Call Manager. The CCM''s FTP and SFTP servers also allow the switch to push the files to the CCM'.

1.4.7 FTAM

(Available by special order only – separate license fee)

File Transfer Access and Management (ISO 8571) is used for collection of files over an X.25 interface, or RFC1006/IP for switches that support this option.

1.5 File Formats

When AMA (Automatic Message Accounting) or BAF (Billing AMA Format) records are collected into files, they may be stored in their original file format or converted to a different format for compatibility with the downstream server. The possible file formats are:

1.5.1 AMATPS

Complete AMA records are packed into 1531-byte fixed size blocks with header and trailing pads. The AMA records may have Recording Office Type/ID and/or Sensor Type/ID fields suppressed. This is the file format sent by the switch when using AMATPS protocol.

www.microtronix.com 8

Microtronix Access - CDR Collection Manager

1.5.2 AMATPS +fileHeader

This format is the same as AMATPS, but also includes the 20-byte file header sent by the switch.

1.5.3 Martin Group

This is a custom AMATPS format used for compatibility with older Martin Group mediation/billing systems. The AMATPS blocks are rounded to the nearest multiple of 512 bytes containing actual records.

1.5.4 AMA

AMA records are packed into the file without block/file headers or trailing pads. AMA records are BAF format with Sensor Type/ID fields suppressed (two-field suppression), or Sensor and Recording Office Type/ID fields suppressed (four-field suppression).

1.5.5 BAF

Billing AMA Format records are packed into the file without block/file headers or trailing pads. When converting from AMA formats, records will have suppressed fields inserted from configured values.

1.5.6 XFER fixed block

Complete BAF records are packed into 2048-byte fixed size blocks with a block header and trailing pads after the last record to the end of the block. This is the file format sent by the switch when using XFER protocol.

1.5.7 XFER variable block

XFER files from the DMS may have trailing pads removed from the fixed-size blocks to create files with variable-size blocks.

1.5.8 EMI

AMA and BAF records can be converted to EMI format and may be divided into “billing” and “access” files for delivery to different servers.

1.6 File Forwarding Protocols

Standard IP-based file transfer protocols ensure compatibility with modern mediation, billing, and application servers. Each collector can be configured with a unique file server IP address and file transfer protocol for client (push), or a unique account for remote client login and pull. For additional security on the IP network, files may be encrypted with Gnu Privacy Guard (GnuPG) before being transferred. The supported protocols are:

1.6.1 FTP

RFC959 File Transfer Protocol

1.6.2 SFTP

SSH File Transfer Protocol

1.6.3 SCP

Secure Copy using SSH

www.microtronix.com 9

Microtronix Access - CDR Collection Manager

1.7 Poll Scheduling

A flexible scheduler allows polling of each switch at any time of day, or multiple times per day as frequently as once per minute. Schedules for weekdays and weekends can also be configured. The initial schedule for a newly created collector configuration is midnight, local time. Initial EADAS schedules are at 5 minutes, 30 minutes, hourly, and daily corresponding to the poll type.

1.8 Configuration and Management Interfaces

A web interface allows for configuration, management, and monitoring from any Internet browser using HTTP or HTTPS. A command line interface provides additional configuration and management tools, and can be accessed via Telnet, SSH, or serial Console port.

1.9 Internal X.25-TCP/IP Gateway

The CCM has an internal X.25-TCP/IP Gateway that provides the connectivity between a local X.25 WAN port or remote XOT interface and the collection application.

On the Access 4000 models, the second WAN port can also be used to provide X.25/TCP connections to other remote application servers by providing conversion between X.25 and TCP/IP devices, or X.25 encapsulation over TCP (XOT). Refer to the Access User Guide for details.

1.10 Internal Serial/TCP Terminal Server

The Access 1000 & 4000 also have an internal Terminal Server that provides the connectivity between a local serial interface to the switch and the collection application or to remote management applications.

On the Access 4000 models, the second WAN port can also be used to provide serial connections to other remote application servers by providing conversion between serial and TCP/IP devices. Refer to the Access User Guide for details.

1.11 X.25 Interface

The WAN port(s) support synchronous RS232/V.24, V.35, X.21, and RS449/V.36 with speeds up to 10Mbps, in a standard DB25F RS530 connector for X.25 connection to the legacy voice switch.

On the Access 4000 models, Console/WAN port 1 can be used for one of:

● Second X.25 interface for backup/redundancy, or other independent applications

● Second X.25 interface for record collection

● Terminal server interface for serial management connection to the switch

● System console port for configuration and monitoring

In addition, the Console port serves as the console for the boot program, and operates in RS232 asynchronous mode during boot up.

Model 1000-S01 does not have a second port, so the WAN port doubles as the boot console.

If ordered, interface adapter cable(s) for the WAN port(s) will be supplied in the shipped package.

1.12 Serial Interface

The WAN port(s) support asynchronous RS232/V.24 with speeds up to 115.2 Kbps, in a standard DB25F RS232 connector for serial connection to the legacy voice switch.

On the Access 4000 models, the Console/WAN port can be used for one of:

● Interface for record collection

● Terminal server interface for serial management connection to the switch

● System console port for configuration and monitoring

www.microtronix.com 10

Microtronix Access - CDR Collection Manager

1.13 Ethernet Interface

The RJ45 Network interface is 10/100 Ethernet with auto-detection, supporting a rich set of standard IP protocols including TCP, UDP, FTP, SSH, SFTP, Telnet, HTTP, HTTPS, NTP, DNS, etc.

VLAN and secondary IP address configurations are also supported.

1.14 USB-mounted Storage Device

The USB host port supports either a flash drive or hard disk storage device. The device is used for collected files, log files, and configuration backups so may be replaced without loss of functionality. The device may be internally mounted, or externally mounted for easy access.

Removal of a drive should only be performed when the system is not actively collecting, and should be replaced with the original or any compatible device before the next scheduled poll. The drive is formatted with FAT32, and may be installed on any compatible PC for retrieval of files.

1.14.1 GZIP Compression

Collected files can be compressed using Gzip. This can be done prior to FTP forwarding or afterwards. Either way, only the compressed files will be stored in the archive.

1.14.2 GnuPG Encryption & Compression

For additional security, collected files may be encrypted/compressed with Gnu Privacy Guard (GnuPG). This can be done prior to FTP forwarding or afterwards. Either way, only the encrypted files will be stored in the archive.

A public key is used to encrypt the files. The default public key is located on the CCM at:

/.gnupg/pubring.gpg

A private key is used to decrypt the files. The default private key is located at:

/.gnupg/secring.gpg

The default private key may be copied to the server that will be decrypting the files.

New keys can be generated on the server using the “gpg” utility. For example:

$ gpg --gen-key kind of key: RSA (no signature) keysize: 2048 expires: 0 confirm: y real name: CCMkey email: user@server comment: key for CCM confirm: O (okay) passphrase: my-Passphrase-1

Public and private keys are generated, and will be in the ".gnupg" directory in the user's home directory. Copy the public key "pubring.gpg" to the "/.gnupg/ directory of the CCM.

For the strongest security, it is recommended that private keys not be kept on the CCM.

www.microtronix.com 11

Microtronix Access - CDR Collection Manager

2 Quick Start Guide

Configuration of the CCM will require a PC or laptop with an Ethernet port and any standard Internet browser like Windows Internet Explorer or Mozilla Firefox.

Optionally, a serial COM port (or a USB port with a USB serial adapter) on the PC may be used to connect to the Console port to configure default IP address and network parameters. A terminal emulator application like “putty” set for 9600-N-8-1 will be required for this use.

2.1 Package Check List

Check that the package shipped contains the following items.

 Access 1000 or 4000 Gateway unit (CDR Collection Manager model)  AC power adapter and country-specific power cord, or -48VDC power cord  Console Cable (DB9F-DB25M)  RJ45 Ethernet patch cable (blue)  RJ45 Ethernet crossover cable (red)  Optional: custom-ordered WAN cable(s)  Optional: rack mount kit (19” 1U shelf)

2.2 Installation

1) The CCM may be placed on a shelf in a rack. The rackmount model is a 19'' 1U enclosure.

2) Connect the Ethernet patch cable between the RJ45 10/100 Network port and an Ethernet hub/switch.

3) Connect the DB25F WAN port to the X.25 interface of the switch (or to the cable coming from the switch) using the WAN cable. Refer to the WAN Cables section for the correct cable.

4) Optional: Connect the Console port to the COM port of the PC using the Console Cable.

5) Insert the USB Flash Drive if external mount is provided.

6) Connect AC power adapter and AC power cord, or the -48VDC power cord to the supply.

7) Wait 30 seconds for the boot process to complete. The RUN led will start to blink.

2.3 Console Port

The Console Port offers system control access during the boot-up process. Boot up messages will be displayed if a PC COM port is connected using the Console Cable, and the terminal emulator (like “putty”) is set for 9600-N-8-1.

2.3.1 U-Boot Command Access

After power up, there is a 10 second delay that allows U-Boot command access:

Autoboot in 10 seconds (Enter password to stop)...

if the password “foad” is typed while the message is displayed, the U-Boot prompt “A4K:>” will indicate command readiness.

2.3.2 Setting Default IP Parameters

The default IP network parameters may be modified or added here as an alternative to the configuration via the web interface. Enter the following commands to change the default IP address, netmask,

www.microtronix.com 12

Microtronix Access - CDR Collection Manager

default gateway (if needed), and optionally a new system “hostname”

set ipaddr 10.1.1.240 set netmask 255.255.255.0 set gatewayip 10.1.1.1 set hostname MYNAME save boot

These defaults will remain in effect until again changed again in U-Boot, or explicitly changed via the

Ethernet configuration page in the web interface.

2.3.3 Emergency IP Address Recovery

The u-boot console may be used to recover a forgotten or mis-configured IP address. While in in the UBoot console, the default IP address and other parameters may be displayed:

print ipaddr print netmask print gatewayip

If the default values are not in current effect, they may override the system-defined values temporarily by setting new default values (if desired) and entering the U-Boot commands:

set runlevel 2 save boot

When the system starts up, it will be using the default IP address information, and should be reachable on that network. Browse into the web interface and access the Ethernet page to view the “forgotten” values. Restart the system to get the U-Boot console, and reset run level:

set runlevel save boot

The system will restart with the system-defined values.

2.3.4 System Firmware Updates

The u-boot console may also be used in conjunction with Microtronix support for applying system firmware updates, and emergency IP address recovery. (Application firmware updates are available in the Maintenance page of the Web interface.)

To apply system firmware updates:

1) Obtain one or both of the kernel image (uImage) and filesystem image (jffs2.img) files from Microtronix

2) Start a tftpd server on the PC or an available file server

3) Place the file(s) in the tftpd default directory on the PC or server

4) Enter the PC or server IP address (example 10.1.1.200) using the u-boot commands:

www.microtronix.com 13

Microtronix Access - CDR Collection Manager

set serverip 10.1.1.200 save

5) Load the new kernel image:

run updatekernel

6) Load the new filesystem image:

run updatejffs2

7) Start the system by re-applying power or typing the “boot” command.

2.4 Configuration Web Interface

The default IP Address of the CCM is 10.1.1.240. The PC used to access the web interface must be configured (temporarily) for an address in the same subnet, for example, 10.1.1.200. Connect the PC to the same LAN, or temporarily use the red Ethernet crossover cable to connect directly to the CCM.

Open the web browser on the PC, and enter http://10.1.1.240 in the URL field. When prompted by a popup window, login using default user name: admin, and password: admin.

The home page will be displayed with the main menu down the left hand side. The CCM can now be configured by selecting the main menu items. Each page has a Help button in the upper right corner for viewing additional information specific to that page.

2.5 IP Network Configuration

To create or modify the IP network parameters different than the default values defined in U-Boot , obtain the new IP address, network mask, and default gateway values. Follow this procedure only if you don't want the default values to be used in the running system.

1) Select the Ethernet item from the System main menu section to display the configuration form.

2) Modify the Hostname to something meaningful to the collector. The name associated with the switch is best – the Hostname will appear as the default Network Element Name in the CDR Collector configuration form.

3) Click on the Select button beside the desired interface in the Interfaces Table (eth0).

4.a) If using Static IP configuration, obtain the new IP address, network subnet, default gateway, and DNS values from your network administrator. Click on the Static configuration button, and enter the values in the Default Gateway, IP Address, Netmask, and Gateway fields. Click on the DNS button to enter one or more DNS server addresses if domain names are used for email, NTP, or FTP servers.

4.b) If using Dynamic IP configuration, click on the DHCP configuration button.

5) Click the Apply button for the changes to be saved and to take affect.

Connect the Network port to the new network, if not already. Since the IP connection may be lost due to the change, the new address may need to be entered in the browser. The Ethernet configuration page displays the current status of the Ethernet interface.

For more information on additional network configuration, click the Help button on the page.

2.5.1 Verifying IP network

Use ping from another station on the IP network to verify the CCM is reachable. Sometimes ARP cache tables are obsolete and need refreshing after an IP change.

The LAN led on the front panel will blink when there is activity on the Ethernet port.

www.microtronix.com 14

Microtronix Access - CDR Collection Manager

If the PC used for configuration is still able to reach the CCM, use telnet or ssh to connect to the command line interface. If the unit has been pre-configured for system console access on the Console port, you may use a terminal emulator to connect a PC COM port to the console using 9600-N-8-1. Login using user name “root” and password “f0adA” (0=zero).

Type “ifconfig eth0” to view the status and statistics of the Ethernet interface.

Use ping to test the connection to the default gateway or another station on the IP network.

To test the connectivity to a remote IP host that will be connecting to or receiving connections from the CCM, use ping to verify reachability.

2.6 Date and Time Configuration

For accurate polling schedules, the system date and time needs to be set. To set the data, time, and time zone, click on the Date and Time main menu item under the System section.

1) Click on the Change Date and Time button and enter new data and time

2) Click on the Change Timezone button and select the desired time zone

3) Optional: click on the Use NTP button and enter the URL for an NTP server

4) Click on the Apply button to set the new values.

External NTP (Network Time Protocol) server configuration will require a DNS to be configured in the Ethernet configuration page. Time synchronization is scheduled to be called at 15 minutes before midnight. This schedule can be changed in the Edit Config Files page. Use the dropdown list to select “cron scheduler”, open it, and modify the line containing “rc.sysclock”. Save the file.

www.microtronix.com 15

Microtronix Access - CDR Collection Manager

2.7 CDR Collection Manager Configuration

The CDR Collection Manager configuration page is used to configure the switch polling parameters, connectivity, and file delivery for each switch to be supported. Click on the Configure item in the CDR Collector main menu section to display the form and the current values. The page consists of a number of expandable sections that can be opened by clicking on the title for each section, followed by a table of already configured “Collectors”.

For the latest detailed configuration information, click the Help button on the page.

2.7.1 Network Element Name

The Network Element Name should reflect a unique name assigned to each CO switch. Enter a new name in this field to create a “collector” for a switch, or select the name of an already configured “collector” from the table of Collectors to modify an existing one.

This name may be used to form part of the CDR output file name by using the “%n” formatting variable in the Filename Format field. It will be used for identification in email notifications, if enabled.

The FTAM protocol requires the name to be 8 characters or less.

2.7.2 Polling Protocol

This field configures the protocol used by the switch. Choose from the available protocols in the dropdown list when creating a new collector. The displays will change to show parameters relevant to the chosen protocol.

The protocol of an existing switch will be displayed, but not normally changed.

The possible protocols are:

● AMATPS Collection of sequential AMA files.

● BUFFER Buffered collection of raw data over an X.25 or serial interface.

● EADAS Collection of traffic data files (create 1 collector for each interval type).

● FTAM Collection of files over an ISO/FTAM interface.

www.microtronix.com 16

Microtronix Access - CDR Collection Manager

● MTP Collection of files in client (SFI) or server (SFO) mode. It may also be configured

for command line interface. A collector may be created for each.

● SoftSwitch Collection of files over an FTP, SCP, or SFTP / IP interface

(X.25/TCP Gateway parameters do not apply).

● XFER Collection of AMA, SMDR, or other file types (each in a separate collector).

Open the individual sections by clicking on the section name.

2.7.3 Remote Switch Interface

This section shows how to configure the protocol parameters to interface with the switch. When creating a new collector configuration, choose the Polling Protocol used by the switch. The display will change to show parameters relevant to the chosen protocol.

The following sections describe each protocol.

2.7.3.1 AMATPS Protocol Configuration

Configuring for collection from the switch consists of creating a client for pulling files from the switch's AMAT (AMA Transmitter).

The Collector password parameter, consisting of the Recording Office type, unit, and ID fields, is sent to the switch to request a polling session and MUST be correct for the AMAT to accept the connection.

The AMAT password parameter, consisting of the Sensor type, SUN, and ID fields, is sent by the switch' AMAT in response to the connection request and MUST be correct for the Collection Manager to proceed with a polling connection. If set to all zeros, any password is accepted and ignored.

The Sensor type and ID fields may also be used to form part of the output filename, and/or inserted into AMA records if BAF Output Format is selected.

The type, unit and ID fields are 3, 1, 6 digits respectively.

The Poll Retries parameter specifies the number of retries attempted after a first failure.

The X.25/TCP Gateway parameters are used by the collector to connect to the switch's X.25 interface via the local (internal) or a remote X.25/TCP gateway. The X.25 interface of the gateway must be configured with at least one Permanent Virtual Circuit (PVC).

Local (internal) X.25/TCP gateway

www.microtronix.com 17

Microtronix Access - CDR Collection Manager

The IP Address is set to the local IP network interface (127.x.x.x) to address the local gateway which connects directly to the X.25 interface of the switch via a WAN port. The TCP to X.25 Routes section of the internal gateway must listen on the TCP Port Number and map it to PVC 1 on the X.25 interface.

Remote (external) X.25/TCP gateway:

The IP Address is set to the external IP network interface to address the remote gateway which connects to the X.25 interface of the switch via it's local port. The TCP to X.25 route/map of the remote gateway must listen on the TCP Port Number and map it to PVC 1 on the X.25 interface.

www.microtronix.com 18

Microtronix Access - CDR Collection Manager

2.7.3.2 BUFFER Protocol Configuration

Configuring for continuous data collection from the switch consists of creating a client or server daemon for reading data from the switch's interface.

The Read Timeout interval is the number of seconds of idleness (no data received) before the file is closed and a new one opened.

The Maximum File Size value is the maximum number of bytes written to the open file before it is closed and a new one opened. A short time of idleness is allowed so that any partial “record” is not split between files.

If Polling Mode is set to Client, the X.25/TCP Gateway parameters may be configured for connection to the local or a remote X.25/TCP Gateway, or to the local or remote TCP terminal server for serial connection to the switch.

If the gateway or serial server is local (internal), a local IP Address is used (127.x.x.x). If the gateway or serial server is remote (external), the IP Address must be external. The gateway or server must be listening on the TCP Port Number.

If Polling Mode is set to Server, the daemon will accept a connection from any source by configuring the TCP Port Number as the listening port and clearing the IP Address field. If the source is the local X.25/TCP gateway or the Terminal / Sync Server, the TCP port may be bound to a local interface by setting the IP Address to 127.x.x.x.

www.microtronix.com 19

Microtronix Access - CDR Collection Manager

2.7.3.3 EADAS Protocol Configuration

Configuring for collection from the switch consists of creating a client for pulling files from the switch's file server.

Select the traffic report type in the File type field. A separate collector must be created for each traffic report type desired. Each report type has it's own poll schedule (5 minutes, 30 minutes, hourly, or daily). Each also has X.25 interface and file transfer parameters that can be unique or the same.

The X.25/TCP Gateway parameters are used by the collector to connect to the switch's X.25 interface via the local or a remote X.25/TCP gateway.

Local (internal) X.25/TCP gateway

The IP Address is set to the local IP network interface to address the local gateway which connects directly to the X.25 interface of the switch via a WAN port. The TCP to X.25 Routes section of the internal gateway must listen on the TCP Port Number (and bind to the same local IP address)

Remote (external) X.25/TCP gateway:

www.microtronix.com 20

Microtronix Access - CDR Collection Manager

2.7.3.4 FTAM Protocol Configuration

Note: FTAM is only available if an FTAM license is purchased.

Configuring for collection from the switch consists of creating a client for pulling files from the switch's FTAM server, or creating a server for receiving files from the switch's FTAM client.

FTAM Client

If polling mode is set to Client, the collector will poll the switch for files.

Fill in the AP-title, AE-qualifier, Presentation / Session / Transport Selector fields as expected by the switch. Fill these as appropriate, paying regard to the expectation in the switch.

The Subnet Address Index field is the reference to the defined RFC1006 sub networks that provide the collector side of the above parameters. See the FTAM Subnets section for definitions.

The Username, Password, and Account fields should be filled in as necessary for the Collection Manager to login into the switch (the Account field is not normally used, so can be left blank in most cases).

The Directory field specifies an absolute or relative path to CDR files (may be left blank if the files are in the home directory of the user).

The File Read Password and File Delete Password fields should match the values configured in the switch (if any) to allow the corresponding file access.

The File Name 1 and 2 fields may be used to specify the file name(s) of the CDR files on the switch. If both are specified, each one will be retrieved at each poll interval. If neither is defined, the collector will

www.microtronix.com 21

Microtronix Access - CDR Collection Manager

do a directory listing to find collectible files names.

If a file name contains a “%Q” or “%q” variable, the Sequence # range and Current seq # parameters can be set to match the range and current sequence number on the switch for that file name. For example, the range on the switch is defined to be 1-500, the number of digits is 4, and the next available file sequence number is 234 (TTFILE0234):

If a file name contains a “%H”, “%h”, or “%d” variable, the Current seq # parameter can be set to match the current date/hour value on the switch for that file name. For example, 9AM (0900) Jan 20, 2015:

The Current sequence number 1 and 2 fields contain the current (next) sequence number if File Name 1 or 2 contain a “%” variable. These fields MUST be given an initial value equal to next available file in the switch. The variable will be expanded into the current sequence number when polling for that file. Successful retrieval will cause the sequence number to be incremented. The variables may be one of:

– %Q – 4-digit sequence number within the defined range

– %q – 6-digit sequence number within the defined range

– %H – 8-digit date+hour tag in the format YYMMDDHH, incremented by 1 hour

– %h – 8-digit date+hour tag in the format YYMMDDHH, incremented by 2 hours

– %d – 8-digit date+hour tag in the format YYMMDDHH, incremented by 24 hours (daily)

The Post-poll Action parameter may be configured for DELETE or RENAME to cause the collection cycle to delete the file from the switch, or rename it using the Rename Extension parameter so that the file is no longer available for collection. Setting to None allows the switch to leave the file available or perform an automatic rotation operation.

The X.25/TCP Gateway parameters are used by the collector to connect to the switch's X.25 interface via the local or a remote X.25/TCP gateway. The Message Encapsulation must be set for RFC1006 (ISO-TP0).

Local (internal) X.25/TCP gateway

www.microtronix.com 22

Microtronix Access - CDR Collection Manager

Remote (external) X.25/TCP gateway:

FTAM Server

If Polling Mode is set to Server, the collector will accept connections and files from the switch.

The Account Username and Password fields in the Local Collector Interface section must be filled in to match the switch so it can login and push files.

At the scheduled poll events, any new files are processed and put into the file forwarding subdirectory for transfer to the billing/mediation server.

The FTAM Local Configuration page provides the common parameters of the FTAM file server. The FTAM Server section defines the listening TCP port number for connections from an X.25 gateway connected to the switch's x.25 interface, or directly from a switch with an IP interface.

www.microtronix.com 23

Microtronix Access - CDR Collection Manager

2.7.3.5 MTP Protocol Configuration

Configuring for collection from the AXE switch consists of creating a client (SFI) for pulling files from the switch's MTP server, or creating a server (SFO) for receiving files from the switch's MTP client. Alternatively, an MTP command line interface (CLI) may be created for converting MTP format to text.

MTP– Session File Input (SFI)

Select Polling Mode = Client if the Collection Manager initiates the polling connection. The collector will poll for files defined in the Base File Name 1 & 2 fields. At least file name 1 must be defined for polling to occur. A sequence number is appended to each file name for unique file retrieval. The range of sequence numbers can be defined, and the next to collect can be set by entering the Current seq # and selecting Update.

The collected file name will be <Base File Name>-<seq#>, for example: “TTFILE00-0234”.

Local (internal) X.25/TCP gateway

Remote (external) X.25/TCP gateway:

www.microtronix.com 24

Microtronix Access - CDR Collection Manager

MTP – Session File Output (SFO)

Select Polling Mode = Server if the Collection Manager waits for the polling connection from the switch. Enter the listening TCP port number in the TCP Port Number field of the X.25/TCP Gateway section. The Message Encapsulation must be set for a type that supports X.25 Q-bit packets like QMBIT, QRBP, or AEPN. These must agree with the setting in the X.25 to TCP Routing table corresponding to the incoming X.25 connection.

At the scheduled poll events, any new files are processed and put into the file forwarding subdirectory for transfer to the billing/mediation server.

MTP – Command Line Interface (CLI)

Select Polling Mode = CLI if the Collection Manager waits for a connection from a remote terminal emulator to convert user commands to MTP format towards the AXE, and deliver the text portion of the response back to the user. This is known as AMTP (Alphanumeric terminal over Ericsson MTP).

X.25/TCP gateway

The IP Address is set to the address or a local or remote gateway which connects directly to the X.25 interface of the switch via a WAN port. The TCP to X.25 Routes section of the gateway must listen on the TCP Port Number.

www.microtronix.com 25

Microtronix Access - CDR Collection Manager

Remote terminal emulator

Select the TCP port number [and binding IP address] on which the CLI interface listens for TCP connections from the remote terminal emulator. A server daemon is started that waits for a user to connect, then connects to the AXE's command line interface via the X.25/TCP gateway defined above.

The daemon issues a “Cmd>” prompt to indicate readiness to accept AXE commands from the user.

www.microtronix.com 26

Microtronix Access - CDR Collection Manager

2.7.3.6 SoftSwitch Protocol Configuration

Configuring for collection from a soft switch consists of creating a client for pulling files from the soft switch FTP/SCP/SFTP server, or creating a server for receiving files from the soft switch FTP/SCP/SFTP client. The X.25/TCP Gateway parameters are not used.

SoftSwitch Client

For FTP client operation, fill in the IP Address, Username, and Password fields for logging into the remote switch.

For SCP/SFTP client operation, fill in the IP Address and Username fields only. Password-less login is used, and the CCM''s SSH public key must be installed on the remote server.

The SSH public key may be retrieved from the CCM at the path:

/.ssh/id_rsa.pub

and the content added to the server file:

<home directory>/.ssh/authorized_keys2

Once copied, the authentication needs to be completed by connecting from the CCM to the server using the ssh command:

ssh <user>@<serverIP>

Answer “yes” if and when prompted to continue.

The File Path field consists of a specific path if the files are not in the user's home directory.

The File Name field consists of a file name, and can include a wildcard (* or ?) file lookup.

The Poll Retries field defines how many additional times an S(FTP) operation is attempted in case of failure.

The Post-poll Action parameter may be configured for DELETE or RENAME to cause the collection cycle to delete the file from the switch, or rename it using the Rename Extension parameter so that the file is no longer available for collection. Setting to NONE allows the switch to leave the file available or perform an automatic rotation operation.

www.microtronix.com 27

Microtronix Access - CDR Collection Manager

SoftSwitch Server

For Server operation, fill in the Account Username and Password fields in the Local Collector Interface section to match the remote switch's FTP/SFTP client so it can login and push files.

At the scheduled poll events, any new files are processed and put into the file forwarding subdirectory for transfer to the billing/mediation server.

www.microtronix.com 28

Microtronix Access - CDR Collection Manager

2.7.3.7 XFER Protocol Configuration

Configuring for collection from the switch consists of creating a client for pulling files from the switch's XFER file server.

The Protocol ID field must be set to a non-zero value to collect files and must correspond with the subsystem value expected by the switch for the type of file collected. The Protocol Type field must be set to the type of file. This should correspond with the subsystem ID type on the switch..

A collector configuration may be added for each of the file types: AMA, SMDR, OM, JF, and DLOG.

Recovery of partial file retrieval due to connection problems is configured using the File Recovery parameter. Normally set to Enabled, but may be set to Disabled to always delete partial files and collect files from the start.

The Poll Retries parameter specifies the number of retries attempted after a first failure.

The Post-poll Action parameter should be configured for Confirm to cause the collector to confirm successfully collected files. The switch will automatically rotate the file so it is no longer available for collection. Setting to None causes the collector to not confirm the file so that the the switch will leave the file available. This will cause the file to be retrieved at every poll interval, so should only be used for testing purposes.

The X.25/TCP Gateway parameters are used by the collector to connect to the switch's X.25 interface via the local or a remote X.25/TCP gateway.

Local (internal) X.25/TCP gateway

Remote (external) X.25/TCP gateway:

www.microtronix.com 29

Microtronix Access - CDR Collection Manager

www.microtronix.com 30

Microtronix Access - CDR Collection Manager

2.7.4 X.25/TCP Gateway

The collector uses a TCP socket to make a connection towards the switch via an X.25/TCP gateway that is, in turn, connected to the switch via an X.25 interface. The gateway may be a remote X.25/TCP gateway, or the internal X.25/TCP Gateway (see the corresponding mapping in the TCP to X.25 Routes page). If the internal gateway is used, the local X.25 interface(s) will be connected to the switch directly and must be configured accordingly (see the X.25 WAN page).

The IP Address parameter specifies the IP address of the X.25/TCP gateway to which a connection will be made. For the internal gateway this will be 127.x.x.x. If Polling Mode is set Server, this is the binding IP address for the TCP listen.

The TCP Port Number parameter specifies the port number on which the X.25 gateway is listening for a connection request. For the internal gateway, it must match an entry in TCP to X.25 Route table. If Polling Mode is set Server, this is the listening port.

The Message Encapsulation parameter specifies how X.25 messages are preserved (encapsulated) over the TCP socket in order to delineate its boundaries. This must agree with the configuration in the X.25 gateway. The MTP protocol must use an encapsulation that handles X.25 Q-bit packets.

By default, The internal X.25 gateway listens on TCP port number 102, and IP address 127.0.0.1 maps to WAN port 0, 127.0.0.2 maps to WAN port 1.

RFC1006 is used as the encapsulation method for most protocols, except MTP which requires Q-MBIT, QRBP, or AEPN; and BUFFER which may require RAW. Refer to the TCP to X.25 Route configuration page to add/modify X.25 call parameters.

If connecting to a remote router supporting XOT, add or modify the corresponding entry in the TCP to X.25 Route table by selecting XOT as the outbound “X.25 device”.

The TCP and IP parameters generally refer to a local or remote X.25/TCP gateway, but in fact may refer to a terminal server, or any other application client/server that supports the selected encapsulation method.

www.microtronix.com 31

Microtronix Access - CDR Collection Manager

2.7.5 FTAM Local Collector Interface (Common)

This section configures parameters for the collector side of the FTAM interface. These parameters will be sent to the switch as the source values.

Fill in the AP-title, AE-qualifier, Presentation / Session / Transport Selector fields as expected by the switch. FTAM collectors will use this set of common parameters if their Subnet Address Index is set to 1. If an additional set of these parameters is required, then these can be defined in the following section, FTAM Subnets Configuration.

The FTAM Server section defines a common FTAM server using the Bind IP address and the Listen TCP port parameters. The initial values allow internal RFC1006/TCP connections from the X.25 Gateway. Remote FTAM switches can login and push files using a collector configured for FTAM Server polling mode.

www.microtronix.com 32

Microtronix Access - CDR Collection Manager

2.7.6 FTAM Subnets Configuration

This section configures additional FTAM parameter sets for the collector side of the FTAM interface.

When the page is first displayed or Reset, the Subnet Number field contains the next available subnet number.

Fill in the AP-title, AE-qualifier, Presentation / Session / Transport Selector fields as expected by the switch. Click the Add/Update button to save these parameters under the Subnet Number displayed. FTAM collectors may use this set of common parameters if their Subnet Address Index is set to this Subnet Number.

To modify an existing subnet, select the desired subnet number in the table at the bottom of the form. The selected subnet will be displayed for editing. Click on the Add/Update button when changes are complete.

To delete an existing subnet, select the desired subnet number in the table at the bottom of the form. The selected subnet will be displayed. Click on the Delete button to remove the subnet.

www.microtronix.com 33

Microtronix Access - CDR Collection Manager

2.7.7 Local Collector Interface

This section configures parameters for the collector side of the interface, and general polling parameters. Only fields and options relevant to the collector's protocol will be displayed. When creating a collector, a local Linux user account will be created for remote clients to push files, or operators to login and manually poll or test the switch interface.

The Account Username and Password parameters are used when creating a local Linux user account for this collector. This account will be used when the collector is configured as a server (FTAM, SoftSwitch) for the remote switch client to login and push files to the collector. If the Username field is left blank when adding a new collector, an account using the Network Element Name will be created. If not specified, the default Password will be the same as the Username. The account name and/or password may be subsequently changed by entering values into the fields.

The Output File Format parameter applies to polling protocols that collect AMA or BAF files in blocked format like AMATPS, XFER, and some soft-switches. For example, the blocked files may be converted to unblocked/streamlined, and AMA records may be converted to BAF.

The Output Filename Format parameter specifies how collected files can be renamed for local storage and forwarding. The parameter consists of a string containing text and replacement variables (%V) for adding sequence number and/or date/time components to the file name. This is mandatory if the collected filename is not unique.

If this field is left blank, the collected file will not be renamed. This not recommended especially where the collected file name is not unique.

The File Sequence Number parameter allows the definition of the starting point for the sequence number variable in Output Filename Format. This is done during installation to set the sequence to match a prior collector, or any time that it needs to be changed. Remember to click the update button for the new number to take effect when the form is applied with the Add/Update button at the bottom.

The Compression Method parameter specifies the compression or encryption method to be applied to collected files when stored.

The Failure notification email parameter is used to define the email address of the person to notify when a collection fails. It is assumed that a compatible SMTP server is available and reachable on the network. A DNS server must be defined in the Ethernet page to resolve the domain name.

www.microtronix.com 34

Microtronix Access - CDR Collection Manager

2.7.8 File Forwarding Service

This section configures the parameters of the mediation, billing, or other application server to which collected files will be transferred.

If File Transfer Method is set to Disabled, collected files will remain on the collector until manually pushed by the user or pulled from a remote server.

The Backup file aging parameter specifies how many days files that have been moved into the backup archive (after successful forwarding) before they are removed from storage. Aging still occurs even when forwarding is disabled. The Maximum backup files parameter specifies a limit on the number files storee in the backup directory. Aging and pruning occur during the daily log rotation scheduled event.

Client

If collected files are to be automatically pushed to a mediation/billing server, Then a client must be chosen (FTP, SCP, or SFTP).

The Duplicate File Action parameter affects the action taken by the collector in case there is a file of the same name on the server. If set to Abort, the collector will not transfer the file; if set to Overwrite, the collector will replace the file on the server with the new file; and if set to Rename, a data/time stamp is added to the file before being transferred.

The Post-transfer Action parameter may be configured for Delete to delete the file, or Backup to save the file in the collector's databackup subdirectory. The Gzip and GnuPG backup options specify that the backup files are Gzip compressed or GnuPG encrypted.

When configured for SFTP or SCP client, the Password field is not used. Instead, the CCM's SSH public key must be installed in the authorized keys file in the user home directory on the server.

www.microtronix.com 35

Microtronix Access - CDR Collection Manager

The SSH public key may be retrieved from the CCM at the path:

/.ssh/id_rsa.pub

and the content added to the server file:

<home directory>/.ssh/authorized_keys2

Once copied, the authentication needs to be completed by connecting from the CCM to the server using the ssh command:

ssh <user>@<serverIP>

answer “yes” if and when prompted to continue.

Local Copy

If collected files are to be automatically moved to a local directory of the user's choice, then select Local copy and enter the local directory to which collected files are to be moved.

The user is responsible for creating the local directory, and any further action on the files once they are moved. The local directory must be on the mounted USB flash drive located at “/mnt/usb1/”.

Server

If files are to be pulled by a remote client, the Server method should be chosen.

For Server operation, fill in the Username and Password fields for creating a local user account into which the remote FTP/SFTP client can login and push files.

The remote client has the responsibility to manage the files, and prevent file duplication by renaming, moving, or deleting the files from the collector's data directory. Successfully retrieved files should be backed up to the directory:

../databackup/

Files moved to this directory will be stored until deleted according to the aging parameter.

Once the File forwarding parameters are configured, the FTP or SFTP service can be tested by opening the FTP Test Push page. Select the collector by it's name and click Open. A form with the defined parameters will be displayed and may be edited for temporary values.

www.microtronix.com 36

Microtronix Access - CDR Collection Manager

Click the Test button to start the file transfer test. I test file will be pushed to the server, then pulled back for comparison.

2.7.9 File Conversion and Distribution

This section configures how collected files are to be converted to a different format, and the distribution of the original and/or converted files. This section may be skipped unless EMI conversion is required.

Conversions are only selectable when the file format is known. Currently available with AMATPS, XFER, and SoftSwitch configurations. AMA or BAF files may be converted to EMI.

www.microtronix.com 37

Microtronix Access - CDR Collection Manager

2.7.10 Redundancy

Each collector configuration can have a redundancy peer in case of failure. One collector is configured as the master and the other is configured as the slave. The master normally does the collection on one X.25 interface to the switch, and the slave connects to another X.25 interface to the switch but waits idly. If the master fails to collect for any reason, the slave takes over the collection.

Master configuration:

When Redundancy Mode is set for Master, the Peer IP Address is that of the slave unit backing it up.

Slave configuration:

When Redundancy Mode is set for Slave, the Peer IP Address is that of the master unit that it backs up.

The redundancy process uses a secure SCP connection to exchange status and any sequence number files used during collection. The public key of each unit must be installed in the authorized keys file of it's peer for password-less login. To locate each others files, both the slave and the master must have the same Network Element name, so that the underlying directory tree is the same.

Redundancy is only relevant for client configurations. A pair of units with server configurations can both be active at the same time. The switch itself would select one or the other of it's 2 interfaces.

www.microtronix.com 38

Microtronix Access - CDR Collection Manager

2.7.11 Poll Schedule

When a collector is first added, a default polling schedule is created for midnight of the configured timezone. This schedule can be changed in the Poll Schedules page. If a collector configuration is deleted, the schedule is also deleted.

It is recommended that an NTP server be defined in the Date and Time page to keep the collector's time coordinated.

The default EADAS collection schedules are 5 minutes, 30 minutes, hourly, or daily, depending on the File type.

www.microtronix.com 39

Microtronix Access - CDR Collection Manager

2.8 X.25 WAN Port Configuration

Configure each WAN port to match the attached switch's X.25 interface at all 3 layers of the X.25 protocol. The unit is pre-configured to work in most installations, but verifying the paramaters is recommended.

2.8.1 Layer 1 – Physical

1) From the main menu X.25 WAN section, select L1-Device to display the form.

2) Select hdlc0 from the device drop-down list (hdlc0 – WAN port 0).

3) Select the physical interface type to match the switch's X.25 interface.

4) For connection to a DTE device like a switch, select Internal Clock Source and an appropriate rate (usually 64000). If the switch is generating clock (DCE), select External Clock Source.

5) Some switches like the DMS do not support an outbound DTR signal on its X.25 interface. If so, then select DTR Detection: OFF.

6) Click the Status: Enable button

7) Click the Update button for the changes to be saved.

For additional information, click the Help button on the page.

Layer 1 defaults by switch polling protocol

AMATPS EADAS FTAM MTP XFER Interface Type Clock Source Clock rate DTR Detection

RS232/V.24 RS232/V.24 V.35 V.35 V.35

Internal Internal Internal Internal Internal

64000 64000 64000 64000 64000

ON ON ON ON OFF

2.8.2 Layer 2 – Data Link

1) From the main menu X.25 WAN section, select L2–LAPB to display the form.

2) Select hdlc0 from the device drop-down list (hdlc0 – WAN port 0).

3) If the switch is configured as a DTE, select DCE; if configured as DCE, select DTE.

4) Configure the Window Size to match the switch X.25 interface.

5) Click the Update button for the changes to be saved.

For additional information, click the Help button on the page.

Layer 2 (LAPB) defaults by switch polling protocol

Mode Window size (k)

www.microtronix.com 40

AMATPS EADAS FTAM MTP XFER

DTE DTE DCE DCE DCE

3 3 7 7 7

Microtronix Access - CDR Collection Manager

2.8.3 Layer 3 – Packet

1) From the main menu X.25 WAN section, select L3–X.25 to display the form.

2) Select a device from the drop-down list (hdlc0 – WAN port 0 is the default).

1) If the switch is configured as a DTE, select DCE; if configured as DCE, select DTE.

1) Configure the packet and window sizes to match the switch X.25 interface. A mis-match may

cause packet layer resets and data loss.

2) Configure SVC and PVC settings to match the switch X.25 interface. A mis-match may cause unanswered call requests.

3) Click the Restart WAN Interface checkbox to cause all the changes to take affect.

4) Click the Update button for the changes to be saved and take affect.

For additional information, click the Help button on the page.

Layer 3 (X.25) defaults by switch polling protocol

AMATPS EADAS FTAM MTP XFER Mode Packet Size Window Size PVC number(s) Number of SVC

DTE DTE DCE DCE DCE

512 512 128 128 512

3 3 2 2 3 1 2,3 0 0 0 0 0 8 8 1

2.9 Verifying X.25 Interface

The WAN led on the front panel will illuminate when the X.25 link is established at all 3 layers of WAN port 0. To view detailed status of each layer of the X.25 interface, select the Status item of the X.25 WAN section. Start at the top level and work down to troubleshoot.

2.9.1 Layer 3 – Packet

Shows the current status of the packet layer. If in “r1:Ready” state, then all 3 layers are established. If not, then:

● There is saved configuration that has not become effective with a restart. Restart the interface.

● There is a problem at the lower levels.

● The attached device does not support X.25.

2.9.2 Layer 2 – Data Link

Shows the current status of the data link layer – should be in “Info Transfer” state. If not, then:

● There is a problem at the lower level.

● The emulation mode (DTE/DCE) is not set correctly.

www.microtronix.com 41

Microtronix Access - CDR Collection Manager

2.9.3 Layer 1 – Physical

Shows the current operational mode, status of the interface signals, and interface statistics.

If the current mode does not match the configuration, then the port needs to be restarted.

If the asserted signals (DSR, CD, CTS) are OFF, then the port is disabled and needs to be configured to be enabled.

If the received DTR and RTS signals are off, then:

● The cable is not connected.

● The cable is the wrong DTE/DCE gender or wrong pinout for the interface.

● The interface is the wrong type (X.21 uses balanced signals, RS232 & V.35 use unbalanced).

● The switch X.25 interface is disabled.

If the received DTR is off and RTS is ON, then the attached device may not support a DTR output signal. If this is the case, then the port must be configured to ignore DTR (DTR Detection: OFF)

If the statistics show an increasing number of receive errors, then the interface type or clocking source may not be correct.

If there is transmit bytes/packets but no receive bytes/packets, then there may be a cable issue or a problem with the attached device which may have become disabled and needs a restart.

www.microtronix.com 42

Microtronix Access - CDR Collection Manager

2.10 TCP to X.25 Routing Configuration

If the CDR Collection Manager is polling the switch for CDR/AMA files, then it initiates the X.25 connection by issuing a localhost (127.x.x.x) TCP connection to the internal X.25 gateway. The parameters for the X.25 connection to the switch are specified in the TCP to X.25 Route section. There is a pre-defined route that can be edited for some X.25 specifics like called/calling addresses

To add or modify a TCP to X.25 mapping entry to the routing table, select TCP to X.25 Routes in the X.25 Gateway section of the main menu to display the configuration form and current TCP to X.25 routes. If modifying an existing route, select the Edit button to the right or the entry in the table below the form.

A backup X.25 link may be configured by adding a second entry with the same listening port, and a different destination device. The other outbound connection information may be the same or different. For example, the primary X.25 link may be WAN port 0 (hdlc0), and the backup link may be WAN port 1 (hdlc1), or a link on a remote X.25 gateway by selecting the XOT device.

2.10.1 Identify inbound TCP/IP connection

Identify the TCP/IP parameter(s) that will be used to match the incoming connection from the collector(s). These MUST match the value in the X.25 Gateway CDR Collector configuration page.. Fill in the left side of the form:

1) Specify the TCP port configured in the X.25 Gateway section of the CDR Collector configuration page in the Listening TCP Port field. Usually port 102.

2) In the Remote IP Address field, enter the localhost address, 127.0.0.1, for connection to port 0 or 127.0.0.2 for port 1.

2.10.2 Specify Conversion or Encapsulation Method

Choose from the drop-down list in the Conversion Type field, the method for this connection. This method MUST match the value in the X.25 Gateway CDR Collector configuration page.

1) Q-MBIT/QRBP/AEPN when the polling protocol is MTP.

2) RFC1006 when the the polling protocol is AMATPS, EADAS, FTAM, or XFER

2.10.3 Generate outbound X.25 connection

Specify the X.25 parameters used to connect to the switch. Fill in the right side of the form:

1) Select the device connected to the X.25 interface of the switch (WAN port 0 or 1). If the switch is connected to a remote router providing X.25 Over TCP encapsulation, select XOT and specify the IP address of the remote router.

2) Choose the connection type (usually SVC, but AMATPS and EADAS use PVCs)

3) Specify the called and calling X.25 addresses to be used in the outbound call request or the PVC logical channel number to be assigned (AMATPS uses PVC 1, EADAS uses PVC 2,3, ...).

4) If SVC, specify user data and facilities as required. FTAM may require Called/Calling Address extension DTE facilities.

Add the new entry to the displayed table at the bottom by clicking Add Entry.

Update the existing entry in the displayed table at the bottom by clicking Update Entry.

Click on Save and Apply Changes button for the entry to be saved and become active.

For additional information, click the Help button on the page.

www.microtronix.com 43

Microtronix Access - CDR Collection Manager

TCP to X.25 route defaults by switch polling protocol

AMATPS EADAS FTAM MTP XFER Listening TCP Listening IP Conversion Device (WAN) Connection type Local LCN (PVC) Called address Calling address Call User Data

102 102 102 102 102

127.0.0.1 127.0.0.2 127.0.0.1 127.0.0.1 127.0.0.1

RFC1006 RFC1006 RFC1006 Q-MBIT RFC1006

Port 0 Port 1 Port 0 Port 0 Port 0

PVC PVC SVC SVC SVC

1 2,3,... n/a n/a n/a n/a n/a 00000000 00000000 00000000 n/a n/a 00000000 00000000 00000000 n/a n/a 03:01:01:00 C0:00:00:00

www.microtronix.com 44

Microtronix Access - CDR Collection Manager

2.11 X.25 to TCP Routing Configuration

If the switch initiates a CDR/AMA file transfer (supported features of FTAM and MTP), then an X.25 to TCP routing must be configured to connect the inbound X.25 connection to the collection application via the localhost IP address.

To add an X.25 to TCP mapping entry to the routing table, select X.25 to TCP Routes in the X.25 Gateway section of the main menu to display the configuration form, and current X.25 to TCP route entries. An entry can be added to the X.25 to TCP Routing table, or an existing entry modified. If modifying an existing entry, click on the Edit button beside the entry in the table below the form.

2.11.1 Identify inbound X.25 connection

Specify the call request parameter(s) that will be used to identify the incoming X.25 call request. This is usually the physical port (device), and the X.25 called address. Fill in the left side of the form:

1) Select the device on which the call request is going to be received (usually hdlc0)

2) Choose connection type: Switched Virtual Circuit

3) Enter destination X.25 address in the Called Address field

2.11.2 Generate outbound TCP/IP connection

Specify the TCP/IP host to which the call will be connected. Fill in the right side of the form:

1) Specify the loopback IP address (127.0.0.1) in the Remote IP Address field.

2) Specify the TCP port number on which the collector is listening in the Remote TCP Port field (usually 4102 – must match the Collector application configuration).

2.11.3 Specify Conversion or Encapsulation Method

Choose from the drop-down list in the Conversion Type field, the method for this connection. This method MUST match the value in the X.25 Gateway CDR Collector configuration page.

1) Q-MBIT (for MTP protocol only)

2) RAW for (BUFFER protocol)

3) RFC1006 (recommended for all other collection protocols)

Add the new entry to the displayed table at the bottom by clicking Add Entry.

Update the existing entry in the displayed table at the bottom by clicking Update Entry.

Click on Save and Apply Changes button for the entry to be saved and become active.

For additional information, click the Help button on the page.

www.microtronix.com 45

Microtronix Access - CDR Collection Manager

2.12 Test Poll

A test poll may be done at any time after installation and configuration is complete. Test polls retrieve special files or directory listings of the switch CDR storage without actual CDR file retrieval.

Before starting, make sure that the X.25 cable is connected and that the X.25 is operational by checking the X.25 status. Correct any issues before proceeding.

Open the Test Poll page and click on the Start button of the desired collector in the displayed table. Test polls are usually very quick (a few seconds), so if there is long delay, there may be a problem with the X.25 or CDR/switch configuration. If the test succeeds, a primary poll should work and can be done now, or can wait for the next scheduled poll event.

If the test poll fails, there is probably an issue with the X.25 configuration, the X.25 gateway routing, or the CDR switch configuration. Check the system log for possible cause of failure. If the cause cannot be readily identified, it may be necessary to monitor the X.25 exchange between the switch and the collector.

To monitor the X.25 traffic, open a Telnet or SSH session to the CCM. It is best to log the session with the appropriate option when invoking Telnet. When prompted, login using “root” and password “f0adA”. Enter the following command at the “#” prompt:

# x25trace hdlc0

Start the test poll again, and observe the trace output. It is beyond the scope of this document to provide protocol analysis, so if required, the output can be captured and sent to Microtronix support for analysis. For the second X.25 link, use hdlc1.

To monitor the internal TCP/IP localhost (loopback) connection, enter the following commands:

# cd /tmp # tcpdump -i lo -w ccm.pcap tcp port 102

Type CTRL-C to stop the trace. Only run the trace for a short time as the “tmp” file system may fill. The file may be pulled from the CCM using FTP, SFTP, or SCP. The file may also be pushed to a PC or file server using SFTP or SCP:

# scp ccm.pcap USER@IP-ADDRESS:[DIRECTORY] <enter password>

Run Wireshark on the PC to view the capture. Especially useful for viewing interpreted FTAM messages.

www.microtronix.com 46

Microtronix Access - CDR Collection Manager

3 Advanced Configurations

The Access CCM supports X.25 link backup, multiple collectors, as well as additional applications using the embedded X.25/TCP Gateway or Terminal Server applications.

3.1 X.25 Link backup

The following diagram illustrates the physical connections and internal logic to configure the Access 4000 CCM for backing up a primary X.25 link using the second WAN port as a secondary link (assuming the Switch supports this).

Main menu item: CDR Collector – Configure

– define a collector and set the X.25 Gateway TCP/IP parameters to 127.0.0.1 : 102

Main menu item: X.25 Gateway – TCP to X.25 Routes

– map 127.0.0.1 : 102 to Port 0 + appropriate X.25 settings for this link (primary)

– map 127.0.0.1 : 102 to Port 1 + appropriate X.25 settings for this link (secondary)

Main menu item: X.25 WAN – L1, L2, L3

– configure Port 0 to match the switch's primary X.25 interface

– configure Port 1 to match the switch's secondary X.25 interface

3.2 Second X.25 Collection Interface

The following diagram illustrates the physical connections and internal logic to configure the Access 4000 CCM for 2 collectors to the same switch or 2 switches. The first collector may be configured for AMA/CDR, the second for Traffic or other data. Each collector configuration can have the same or independent IP servers.

Main menu item: CDR Collector – Configure

– define collector 1 and set the X.25 Gateway TCP/IP parameters to 127.0.0.1 : 102

– define collector 2 and set the X.25 Gateway TCP/IP parameters to 127.0.0.2 : 102

Main menu item: X.25 Gateway – TCP to X.25 Routes

www.microtronix.com 47

Microtronix Access - CDR Collection Manager

– map 127.0.0.1 : 102 to Port 0 + appropriate X.25 settings for the first link

– map 127.0.0.2 : 102 to Port 1 + appropriate X.25 settings for the second link

Main menu item: X.25 WAN – L1, L2, L3

– configure Port 0 to match the switch's first X.25 interface

– configure Port 1 to match the switch's second X.25 interface

3.3 Multiple Collectors on a Single X.25 Interface

The following diagram illustrates the physical connections and internal logic to configure the Access CCM for multiple collectors to the same X.25 interface of the switch. The collectors may be configured for AMA/CDR, Traffic, or other data. More than one collector can share a TCP to X.25 Route.

Main menu item: CDR Collector – Configure

– define collector 1 and set the X.25 Gateway TCP/IP parameters to 127.0.0.1 : 102

– define collector 2 and set the X.25 Gateway TCP/IP parameters to 127.0.0.2 : 102

– define collector 3 and set the X.25 Gateway TCP/IP parameters to 127.0.0.2 : 102

Main menu item: X.25 Gateway – TCP to X.25 Routes

– map 127.0.0.1 : 102 to Port 0 + appropriate X.25 settings for this route (collector 1)

– map 127.0.0.2 : 102 to Port 0 + appropriate X.25 settings for this route (shared by 2 and 3)

Main menu item: X.25 WAN – L1, L2, L3

– configure Port 0 to match the switch's X.25 interface

3.4 Separate Application on Second Interface of the Access 4000

The following diagrams illustrate the physical connections and internal logic to configure the Access 4000 CCM for separate applications to the same switch. The first X.25 interface is configured for CDR collection, and the second interface (port 1) s configured to support an external application like a management server using a command line interface.

www.microtronix.com 48

Microtronix Access - CDR Collection Manager

3.4.1 X.25 – TCP Conversion

X.25/TCP conversion for an application using a TCP socket (RAW or Telnet) for command line interface. Any TCP port number could be used by the server for the CCM to listen on. The example configuration uses 4001.

Main menu item: X.25 Gateway – TCP to X.25 Routes

– map TCP port 4001 to Port 1 + appropriate X.25 settings for this route

Main menu item: X.25 WAN – L1, L2, L3

– configure Port 1 to match the switch's X.25 interface

3.4.2 X.25 Over TCP (XOT)

For application servers that support X.25, XOT may be used for X.25 network replacement with an IP network using XOT. The diagram below shows an external X.25/TCP Gateway that supports XOT (like the Access 1000 X.25/TCP Gateway) being used to bridge the X.25 interface of the server over an X.25 over TCP (XOT) network. The server may also support XOT directly.

Main menu item: X.25 Gateway – TCP to X.25 Routes

– map TCP port 1998 / XOT to Port 1 + appropriate X.25 settings for this route

Main menu item: X.25 WAN – L1, L2, L3

– configure Port 1 to match the switch's X.25 interface

3.4.3 Serial Terminal Server

Alternatively, the second interface (port 1) may be configured for serial/async operation and use the embedded terminal server as in the diagram below. The application server could use a TCP socket, or a serial interface to a local terminal server. Any TCP port number could be used by the server for the CCM to listen on. The example configuration uses 4001.

www.microtronix.com 49

Microtronix Access - CDR Collection Manager

Main menu item: Terminal Server – Serial - TCP

– configure Port 1 Network Settings for TCP/IP 0.0.0.0 : 4001 + appropriate serial settings

www.microtronix.com 50

Microtronix Access - CDR Collection Manager

4 WAN Cables

The WAN port has a DB25F connector with RS530 DCE pin configuration (compatible with ISO 2110). RS232 is a subset of RS530, so the WAN port has a standard RS232 pin configuration when configured for RS232. An adapter cable is required for X.21, V.35, and RS449/V.36.

4.1 Connecting to a DCE

These cables are used when connecting to an X.25 interface configured as a physical DCE supplying clocking on the DCE transmit and receive clock pins.

DCE crossover cable part numbers

W4025-V24-DTE DB25M-DB25M RS232/V.24 crossover cable W4025-V35-DTE DB25M-M34M V.35 crossover cable W4025-X21-DTE DB25M-DB15M X.21 crossover cable W4025-RS449-DTE DB25M-DB37M RS449/V.36 crossover cable

4.2 Connecting to a DTE

These cables are used when connecting to an X.25 interface configured as a physical DTE that expects clocking on the DCE transmit and receive clock pins. If replacing a modem, avoid any modem handshake issues by configuring the switch's X.25 interface type for “leased line”, “permanent modem”, or “direct connect”.

DTE straight through cable part numbers

811-SC6MF DB25M-DB25F RS232/V.24 straight through cable W4025-V35-DCE DB25M-M34F V.35 straight through cable W4025-X21-DCE DB25M-DB15F X.21 straight through cable W4025-RS449-DCE DB25M-DB37F RS449/V.36 straight through cable

www.microtronix.com 51

5 Contact Microtronix

Microtronix Datacom Ltd. 4056 Meadowbrook Drive, Unit 126 London ON N6L 1E3 CANADA

Tel: +1 519 690-0091 Fax: +1 519 690-0092

General Inquiries: info@microtronix.com Sales Enquiries: sales@microtronix.com Customer Support: support@microtronix.com

Microtronix Access - CDR Collection Manager

www.microtronix.com 52

MICROTRONIX Access 1000, Access 4000 Quick Start Manual

Specifications and Main Features

Frequently Asked Questions

User Manual