Netlog - "the call logging buffer with an IP number" New! - Netlog has undergone a major hardware revision, resulting in a new hardware package which is a fraction of it's original size.
Or capture data with a direct TCP connection -

Netlog is our top end call logging buffer featuring SNMP management and SNMP Traps for important alarm events such as 'no incoming data' and 'mains-fail'. It allows a corporate LAN/WAN to be used as the transport medium for PABX call records and alarms. It is designed for use at remote PABX locations, where the call records and alarms originate, and sends them to a central site, where they are processed. Remote units provide two completely independent links from the PABX, to allow both call records and alarm information to be transferred to different central system locations. Netlog is fitted with a battery backed buffer and an Ethernet network attachment, and replaces the traditional PSTN dial up or leased line data collection methods. Netlog provides rugged, error free transfer of data from any point to any other point on the users network.

Easy setup.

Configure Netlog using our Windows based utility - simply enter the IP number of the unit and press GET to see all the current settings. Change as required and press PUT to save the new settings to the unit. The VIEW DATA button allows data to directed to a window on the workstation to verify correct operation.

A screen shot of the Netlog configuration utility

Data retrieval - real-time delivery method.

Call records from the PABX are temporarily stored in the remote units' battery backed buffer. Netlog sends the records across the network to the Piper unit at the central site, and optionally, adds site identifying headers. 

The system can of course carry any form of data including system alarms. If the PABX alarm port allows management functions (MMI), then central management is easily accomplished.

Data retrieval - TCP connection.

This method eliminates the Netlog master unit. Call records from the PABX are stored in the remote units in series of data files. The call logging system at the central site retrieves these files when it is ready using a TCP/IP file transfer protocol. The remote units' memory size may be chosen to suit the level of data activity at the remote site and polling can be done whenever it is deemed necessary. Power failure at the remote site, including ultimate failure of the battery backed power supply will not cause data file loss. The file transfer protocol provides an error free transfer which is much faster than modem transfer.

Reliable data delivery.

Whichever method of data delivery is chosen, Netlog ensures that fault conditions will not cause data loss. All network packets are sequence numbered and acknowledged to ensure totally reliable data delivery.

Hardware Features

Data Buffer -
An appropriately sized RAM buffer, logically located between the call logging port and the network port, is allocated. The data passing through the RAM buffer is also copied to flash memory to ensure complete safety in the event of a long duration power fail (e.g. transit from site to site).

Battery backup -
The power supply will be a no break battery backed supply utilising a sealed lead acid battery, switched mode PSU and intelligent charger. The battery will be sized to allow a minimum of four hours of operation without mains supply. (This time may be increased while affecting battery size, weight and price). The power supply will visually indicate loss of mains and provide this indication on an output signal which will be monitored by the system software. It, and the industrialised case, ensure EMC compliance.

Auxiliary ports -
Up to three additional serial ports may be specified. These can be configured as input ports with their own data buffer, or as outputs ports used to monitor and control other remote equipments. These ports may also be used to manage the system locally.

Network port -
UTP 10Base-T Ethernet port.

Controls and indications -
A hard reset push button, in a discrete location. Power and led indicators on the front panel. An VGA output allows the connection of a monitor to allow terminal software to be run on the unit, taking over console and display duties for fault finding purposes.

Physical -
Metal enclosure, internal no break power supply, 110V / 230Vac input, mains entry on IEC ('kettle') socket. Filtering and bonding as required to ensure EMC compliance.
All ports presented on the back panel, indicators on the front panel.
Free standing and rack mount options.

Software features -
All programs and configuration files are managed by a DOS compatible operating system and a flash file system

Buffer modes -
Incoming call log data buffered in RAM on its way from the call logging input to the output LAN port. It is also copied to a flash file. In the event of network failure the data will be continue to be written to flash file, up to its nominal capacity, and will be automatically unloaded from it when normal service is resumed.
In the event of a network failure, a new flash file will be opened and the previous one closed each day. The daily files will be overwritten monthly, or less often as allowed by flash file system size.

Data transport -
LAN - TCP/IP protocol suite support, allows the unit to forward the call logging data across a routed Wide Area TCP/IP Network. ICMP and ARP are supported. A proprietary protocol providing error free connection orientated data delivery, is carried by UDP datagrams.

Power fail monitoring and failure recovery -
Mains failure is signalled to the system software and a mains failed indicator is lit.
A watchdog software function is provided to ensure that the unit is running its program correctly. In the event of a failure the system will be restarted. A small amount of data not yet stored to flash file or arriving during the restart period may be lost.

Management - Phase I - by menu -
Management of the units is by entering 'command mode', type ++++ at a rate less than 10cps on a serial port. This mechanism allows the configuration of all network connected units to be examined and changed. Also by this means connections can be made to any auxilliary port on any unit for the purposes of controlling equipment connected to these ports.
All management, data collection and auxilliary port connections to be password protected. Master password for the unit and optional passwords per auxilliary port.

Management phase II - by TFTP -
This avoids menu dialogues and replaces them with a view of the files residing in the flash file system. A PC resident (Windows) application will allow Directory functions such as DIR, COPY and DEL to be executed from any networked workstation running a TCP/IP stack. The files resident in the call logging unit will comprise executables, configuration and script files. To change configuration upload new configuration files. To change the function upload new executables or scripts.

Data filtering and manipulation -
Incoming call log data can be pre-processed by the unit to accomplish many purposes (e.g to remove specific calling extension nos). This processing will be by special to type software modules designed for the task.
Data filtering and manipulation - Phase II -
The processing functions will be controlled by script files TFTPed to the unit.

Models -
Configuration -Two serial ports, one for CIL data input, one for management.
One TCP/IP 10Base-T, UTP, network port.
4 hour battery backed up power supply.
Solid state data buffer and program storage. Memory options:-
Buffer sizes available from 4Mb up to 32Mb. Larger buffer sizes available on request.

Return