MICROTRONIX access 1000 series User manual

Microtronix
Access 1000 and 4000
CDR Collection Manager
Quick Start Guide 0.9.5
4056 Meadowbrook Drive, Unit 126
London ON N6L 1E3
C N D
www.microtronix.com
[phone]

Microtronix ccess - 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. 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.1 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 ccess - CDR Collection Manager
2. Configuration Web Interface........................................................................................................1
2.5 IP Network Configuration............................................................................................................1
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...................................................................................................... 0
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............................................................................................................... 1
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........................................................................................... 3
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........................................................................................... 5
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.................................................................................................................................... 6
3 dvanced Configurations................................................................................................................47
3.1 X.25 Link backup......................................................................................................................... 7
3.2 Second X.25 Collection Interface................................................................................................ 7
3.3 Multiple Collectors on a Single X.25 Interface............................................................................. 8
3. Separate Application on Second Interface of the Access 000................................................... 8
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 W N Cables...................................................................................................................................... 51
www.microtronix.com 3

Microtronix ccess - CDR Collection Manager
.1 Connecting to a DCE.................................................................................................................. 51
.2 Connecting to a DTE...................................................................................................................51
5 Contact Microtronix..........................................................................................................................52
www.microtronix.com

Microtronix ccess - 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 ccess - CDR Collection Manager
process, and reduces the exposure to network outages.
The Access 000 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 Gatewa is an example
of an XOT Gateway.
www.microtronix.com 6

Microtronix ccess - CDR Collection Manager
1.3.3 Remote X.25/TCP Gateway Network
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 ccess - 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 ccess - 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 20 8-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 ccess - 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 000 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 ccess 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 000 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 ccess User Guide for details.
1.11 X.25 Interface
The WAN port(s) support synchronous RS232/V.2 , V.35, X.21, and RS 9/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 000 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.2 with speeds up to 115.2 Kbps, in a standard
DB25F RS232 connector for serial connection to the legacy voice switch.
On the Access 000 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 ccess - CDR Collection Manager
1.13 Ethernet Interface
The RJ 5 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 SB-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 ccess - 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 000 Gateway unit (CDR Collection Manager model)
AC power adapter and country-specific power cord, or - 8VDC power cord
Console Cable (DB9F-DB25M)
RJ 5 Ethernet patch cable (blue)
RJ 5 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 RJ 5 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.
) 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 - 8VDC 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 “A K:>” 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 ccess - 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 U-
Boot 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
) Enter the PC or server IP address (example 10.1.1.200) using the u-boot commands:
www.microtronix.com 13

Microtronix ccess - 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).
.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 ddress, 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.
.b) If using Dynamic IP configuration, click on the DHCP configuration button.
5) Click the pply 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 1

Microtronix ccess - 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
) Click on the pply 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 ccess - 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 drop-
down 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 ccess - 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 M TPS 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 M T 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 ccess - CDR Collection Manager
The IP ddress 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 ddress 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 ccess - 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 ddress 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 ddress 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 ddress to 127.x.x.x.
www.microtronix.com 19

Microtronix ccess - CDR Collection Manager
2.7.3.3 E D S 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 ddress 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:
The IP ddress 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.
www.microtronix.com 20