 |
3Com NBX (TNBXPort)
This 'Collector' is specific to the '3Com NBX'. The first field is the 'IP Address' of the switch.
The next fields are the system 'Username' and 'Password' which are needed to gain access to the call data.
Because this collector has to submit a request for the call data the 'Poll Interval' is the period (in seconds) between requests, the default being 15-seconds.
'Default Date' is the start date for the call data to be collected from the 'Switch'. For example if the NBX has been running for 6-months prior to the installation of aioffice the user has the option to gather all the data available since the switch was installed, however this could well involve a very large volume of data! If the user does not wish to retrieve any historical call data this field should be set to the current day. |
 |
Alcatel Etherlink (TEtherlinkPort)
This ‘Collector’ covers IP versions of the ‘Alcatel 4400’ (later models) and the ‘Omni PCX Enterprise’ (not the ‘Office’ version) switches. The ‘Switch Address’ is the fixed IP address of the ‘Switch’. The switch name can be substituted for the IP address.
The ‘Switch Port’ is normally ‘23’ which is set as the default. The ‘Password’ and ‘Username’ are self explanatory. The defaults are either ‘mtcl’ or ‘mtch’ for both username and password.
The ‘Command Prompt’ field will be of the format ‘(***)switchname>’. The contents of the brackets will always be three numbers and the ‘switchname’ can be a mix of alpha numeric characters including underscores. The user will need to log onto the switch to find out what the command prompt is. The ‘Command Prompt’ must be entered into the field to enable the call logging output.
The two check boxes should be left selected. In the bottom left-hand corner of the window is a ‘Test’ button used to check the connection between the ‘Collector’ and the ‘Switch’.
See note on 'Alcatel' switch outputs. |
 |
Alcatel XML (TAlcatelXML)
This 'Collector' is specific to 'Alcatel' switches using the 'OLD' 'XML' tickets ('Omni PCX Office').
The first field is the 'XML' filename and location, found using the browser button.
The second field is the name and location of the 'POS' file.
As with any other form of file 'Collector', the switch will also write to a 'POS' file which records where to read the data from, the last modified date of the file, etc.
If multiple 'Collectors' are being used to collect from multiple switches, each 'POS' file should have a different 'filename' to avoid any problems when the data is being processed by aioffice.
See note on 'Alcatel' switch outputs. |
 |
Avaya IP Definity (TIPDefinityPort)
i Note: This 'Collector' is only applicable to very old versions of the 'Avaya IP Definity'. The newer switches would use the generic 'IP Server' 'Collector'.
The 'IP Definity' writes call data to a PC. This file is then polled every 15 seconds by the 'Collector', read and moved to the 'Backup Directory'.
To configure this 'Collector' the user browses to the location of the 'CDR' file and selects the filename of the file to be polled. The second field is the location of the 'CDR' file and the third is the location of the backup of the 'CDR' file after it has been read by the 'Collector'.
|
 |
Avaya IP Office (TIPOfficePort)
For the ‘Avaya IP Office’, the ‘Customize Setting’ is the location of the ‘Avaya’ ‘SMDR’ file. The field already contains the default location for this file, however if the ‘Avaya’ software has been installed in a different place, the ‘...’ browse button is used to locate the ‘CSV’ file.
The 'TTelnet' or 'TIPServer' collectors can also be used. |
 |
Avaya / Lucent Network Alchemy (TAlchemyPort)
Enter the fixed IP address in the ‘PBX IP address’ field, overwriting the default entry which is actually a subnet mask. The user should enter the current system password in the ‘PBX Password’ field (the default is ‘admin’).
The setting for the ‘Logging Style’ will depend on the ‘Avaya’ software being used. If the original ‘Network Alchemy’ software is being used, the ‘Avaya Standard Call Log’ should be selected. If however the newer ‘Avaya Delta’ software is installed then the ‘Avaya Type 2 Deltas Logging’ should be selected.
The ‘Connection Timeout’ and ‘Call Timeout’ settings should be left in their default state.
i Note: The Alchemy standard call logging output is very basic therefore the 'Delta' option should be used whenever possible. |
 |
Cisco FTP Server (TCiscoFTPServer)
This 'Collector' is used with the 'Cisco Call Manager' pre v5.
The user must enter the 'Username' and 'Password' to gain access to the call data from the 'Call Manager', plus the 'Port' number being used for the output, by default will be 'Port 21' (FTP).
i Note: Later versions of the 'Cisco' use 'SFTP' and will not work with this 'Collector'. |
 |
Cisco SFTP Server (TCiscoSFTPServer)
This 'Collector' has been specifically written to work with the 'Call Manager v5' and uses a secure FTP protocol.
The only settings required are the 'Username' and 'Password' required to gain access to the call data. |
 |
Emulator Port (TEmulatorPort)
This 'Collector' is only used to emulate a 'Switch' output when running aioffice in demonstration or test mode.
The user selects a 'COL' file using the browser. The call data will then be presented a current data using the original time stamp. |
 |
File Collect - Generic (TFileCollect)
This generic 'Collector' is used for switches which write the call data to a file. The first field is the location of the file which contains the call data.
The 'Filename' will normally have the 'Prefix' 'CDR' but this is not always the case so please check before entering anything into this field.
'Data Delta Days' must always be set to '-1' which indicates yesterdays log file should be read. Do not change this field.
If more than one 'Switch' is in use the 'POS' (Position) filename must have a different name for each 'Switch'. |
 |
Inter-Tel IP Collector (TInterTel)
The first field is the 'IP Address' of the switch. The second field is the 'Port' number being used to output the call data (default being '4000').
The next field is the switch 'Password' required to gain access to the data stream.
The 'Socket Type' field may be ignored, however we strongly recommend the 'Attempt Reconnect...' check box should be ticked. |
 |
IP Server - Generic (TIPServerPort)
This ‘Collector’ is used when connecting from an ‘Avaya IP Definity’ or similar ‘Switch’. The only setting required by this ‘Collector’ is the ‘Port’ number on the ‘Switch’. By default this field is set to ‘5001’. The most commonly used ‘Ports’ are ‘5000’, ‘5001’, ‘9000’ and ‘9001’.
i Note: The ‘Switch’ must be configured to send the call data to the PC running the ‘Collector’, i.e. the ‘IP Address’ of this PC. |
 |
NEC NEAX 2000 - COM Port (TNECNEAX2000)
Anyone familiar with ‘COM Port’ configuration will be familiar with the settings for the ‘NEC NEAX 2000’. Under most circumstances the only setting which may need to be changed is the ‘Com Port’. The remainder of the default settings should be correct, unless the ‘Switch’ defaults have been changed. |
 |
NEC NEAX IP (TNEAXIPPort)
The first field is the 'IP Address' of the NEAX'.
By default the 'Switch Port' will be '60010'.
You may need to consult with the system installer or maintainer for the 'SMDR Device' number as this is switch-specific however in the case of a single device this should be '1'. |
 |
Nortel BCM with CDR Server (TBCM_Dcom)
The only collector setting required for the ‘Nortel BCM’ is the ‘IP Address’ or ‘Machine Name’ of the ‘BCM’ switch. If the user is not familiar with the ‘Nortel BCM’ software configuration, please refer to ‘The Oak Collector - Nortel BCM V3.0’ User Guide. If the ‘Switch’ is running ‘V2.5’ software refer to the ‘Nortel BCM V2.5’ User Guide. |

|
Nortel BCM 50 CDR Client (TBCM50)
The first setting is the 'IP Address' or the 'Machine Name' (if WINS is running on the Domain Controller). The other two fields are the 'Username' and 'Password' for the 'Switch'. Please consult with the 'Switch' installer or maintainer if you do not have these details.
i Note: The 'TBCM50' should be used on all later BCM's (including the 400 series) which do not use 'Dcom'. |
 |
Oak SmartServer (TSmartServer)
The ‘SmartServer’ is part of the Oak ‘SmartApplications’ CTi (CRM) software suite. ‘SmartServer’ uses ‘TAPI’ to actively communicate with the ‘Switch’ rather than the passive collection of data normally employed by our Call Management software.
‘Server Address’ is the ‘IP Address’ of the Server running ‘SmartServer’. Clicking The ‘Defaults for SMDR’ will populate the remaining three fields.
To connect to ‘SmartServer’ the PC must be associated with an ‘Extension Number’, however this need not be a genuine number on the phone system. All the user needs to do is to enter an ‘Extension Number’ well outside the genuine extension range into ‘SmartServer’ set to ‘Do not monitor’. This tells ‘SmartServer’ that this is not a genuine extension, but will enable the ‘Collector’ to log into the application. The ‘Extension’ should be labeled something like ‘Oak’ or ‘OakCollection’ to ensure the ‘fake’ ‘Extension’ is clearly identified.
Once this has been done the user must change the ‘Extension Number’ in the ‘Login’ field to that of the ‘fake’ 'Extension’. The ‘Extension Number’ is located within the string ‘{Ext+202}’, where ‘202’ is substituted by the new number.
The ‘VCE’s’ currently only support ‘SMDR’ output from ‘Switches’ however an ‘Event’ ‘VCE’ translator is currently under development. If the ‘Switch’ event stream is being used, the user should click the ‘Defaults for Events’ button. As with the ‘SMDR’ collection, the user will need to change the ‘Extension Number’ in the ‘Login’ string. |
 |
Realtis / iSDX - Binary IDX Data (TISDXComPort)
This ‘Collector’ is used with the ‘Realtis / iSDX’ range of switches which are outputting call data in ‘binary’ format. Under most circumstances the only setting which may need to be changed is the ‘Com Port’. The remainder of the default settings should be correct, unless the ‘Switch’ defaults have been changed. |
 |
Rugby Clock (TComPortRugbyClock)
This ‘Collector’ is only applicable where the ‘Rugby Clock’ (time signal generated by the atomic clock at the National Physics Laboratory and transmitted from Rugby) are being used. Only ‘Vivista’ sites with ‘DS1000’ and ‘DS2000’ switches would use this facility.
Normally the only setting which may require changing is the ‘Com Port’ number.
The ‘Test’ button is used to confirm the connection. |
 |
Siemens HiPath Trader (THiPathTraderComPort)
This 'Collector' should only be used to connect to a Siemens 'HiPath Trader' switch as it has been specifically written to accommodate the modified switch output.
The setting are identical to any of the standard 'Serial' collectors. |
 |
ShoreTel Collector (TshoreTelPort)
The first field is the location of the ShoreTel 'LOG' file which contains the call data.
The 'Filename' will normally have the 'Prefix' 'CDR' but this is not always the case so please check before entering anything into this field.
'Data Delta Days' must always be set to '-1' which indicates yesterdays log file should be read. Do not change this field.
If more than one 'ShoreTel' 'Switch' is in use the 'POS' (Position) filename must have a different name for each 'Switch'. |
 |
Standard COM Port - Generic (TOakComPort)
This is the default 'Collector' used within 'aioffice CommServer'. Normally the only setting which may need to be changed is the actual 'COM Port' used on the PC. |
 |
Swyx IP-PBX (TSWYXPort)
The ‘Swyx IP-PBX’ ‘Collector’ has four configuration settings. The user must ‘browse’ to the location of the following: -
• CDR Filename - the default is ‘cdr0.txt’. This field should only contain the 'filename' and not the path. If the 'browse' feature has been used to locate the file, the path should be removed from the field!
• CDR File Directory - this is the location (path) of the above.
• CDR Backup Directory - this folder is not created by default. Normally is resides within the ‘CDR’ folder.
The default ‘Poll Interval’ is set to ‘15 seconds’ which has proved to be a reasonable interval.
The ‘Collector’ renames the ‘CDR’ text file to ‘WIP.col’ and processes the data in this ‘WIP.col’ into the required COL file format.
The ‘Test’ button checks for the presence of the files and folders listed in the fields. |
 |
Telnet / IP Client - Generic (TTelnetPort)
This ‘Collector’ enables data to be retrieved from a number of different ‘Switches’, for example the ‘Mitel 3300’ and ‘Samsung DCS’. If the user is unsure how to connect to a ‘Switch’ and a specific ‘Collector’ does not exist, the ‘Telnet Collector’ is an excellent starting point.
This 'Collector' is an 'IP Client' which is less secure means of data exchange when compared with the 'IP Server'.
‘Switch Address’ is the ‘IP Address’ of the ‘Switch’. The ‘Switch Port’ is usually either ‘5000’, ‘5001’, ‘9000’ or '9001’.
The ‘Attempt Reconnect...’ and ‘Send CR on Connect’ should normally be checked. The ‘Test’ button enables the user to check the connection to the ‘Switch’. |
 |
Telnet Port with ‘Start’- Generic (TTelnetPort2)
This ‘Collector’ is used for the ‘Splicecom Maximiser’ and is a variant of the standard ‘Telnet Collector’.
‘Switch Address’ is the ‘IP Address’ of the ‘Switch’. The ‘Switch Port’ is usually either ‘5000’, ‘5001’, ‘9000’ or ‘9001’.
The ‘Command’ field will either be the switch ‘Password’ or a command to initiate call logging output.
The ‘Attempt Reconnect...’ should normally be checked. The ‘Test’ button enables the user to check the connection to the ‘Switch’. |
 |
Text File Source (TTestFileReader)
This ‘Collector’ is only used to demonstrate ‘Active Reports’, which is the real-time call data display within ‘aioffice’. |
 |
Trivial FTP Server - Generic (TTFTPServerPort)
This ‘Collector’ can be used to collect call data for an ‘Avaya Definity’. The default ‘Port’ is ‘69’ (TFTP does not use Port ‘21’). The ‘Working Directory’ field is the location of the files on the ‘TFTP Server’.
‘Allow Overwrite Files’ should only be checked if the ‘TFTP Server’ increments the files i.e. adds call data to the end of the file. If the ‘Server’ opens a new file after each data transfer, then this check-box should be left unticked.
i Note: Whenever possible the 'Definity' should be re-configured to be a 'TCP Client' and the 'TIPServer' should be used instead of this 'Collector'. |
 |
UDP Server (TUDPServer)
This 'Collector' is currently only used in conjunction with the 'Cisco Express'.
The 'UDP' (User or Universal Datagram Protocol) 'Collector' is used to collect data on a pre-defied port from any 'Switch' which broadcasts the call data over the entire network as opposed to using a defined path between two devices as used in TCP/IP. |