Listed Below are many of the prime features of CallRunner:
  • A well-established and evolving application: CallRunner has been in active use for over ten years.
  • While it has been developed for use in Australia, it can be configured for use in another country.  To be fully featured in that country, lists of town names with Zip/Postcodes, telephone exchange prefixes, and service and engineering  numbers applicable to the host country should be first loaded into the application. (The developer can pre-load such data on provision of the data in a delimited format)
  • Its major strength is that it has user-definable processes for defining CCR formats to identify any sequence of call date, call time, call origin, call destination, duration, number calling, number called, number connected to, cell location, cell segment, time zone, call type, and data volume for SMS messages. (see Video of the formatting process)
  • Telephone numbers can be defined to save or not to save the country dialing code - see screen shot of telephone number definition.
  • Telephone numbers formats can be likewise defined to exclude service provider code prefixes, and to identify and include or exclude country codes.
  • Can process multi-row CCR formats where particulars of the call may be listed over two or more rows.
  • Can process extended row formats where the call details of single calls are extended over more than one line - such as Travertine Telephone Interception records.
  • Can process standard CCRs, CCRs with bi-directional calls, reverse call CCRs, and Cell Dumps.
  • Some Call Charge Records do not present with a common time format.  Vodafone (Australia) for example, does not adjust SMS calls to daylight savings time, nor interstate calls to the requested local time zones.  CallRunner will identify and highlight times that are not in the local time zone.  The user has the option to have CallRunner automatically adjust the times to the user's time zone.  Any such modified times, or times left out of sync, remain colour-highlighted in data presentations and reports.
  • Cell dumps can be processed from one or more Cell towers. Cell dump processing, particularly if it involves more than one cell tower, will usually involve many thousands of calls in a brief period. If cell dump calls are being searched to identify mobile numbers used in cell locations on different days to, say, identify a serious serial offender, the call records will be legion. CallRunner has a report that will identify common numbers across the subject locations - see Screen Shots.
  • Can identify 'engineering numbers': numbers that have the same format as mobile telephone numbers but actually signify a technical event.   In Australia, there are many thousands of these engineering numbers in use and they can signify in CCRs call diverts, network switching, and a variety of other technical processes.  The difficulty for anylists is that most of these numbers cannot be visually distinguised from legitimate telephone numbers.
  • Likewise, CallRunner readily identifies 'service numbers', such as Service Provider Help lines, as well as mobile EFTPOS units as used in taxies.  The identification of engineering and service numbers can prevent analysts wasting time on false leads.
  • For Australian users, CallRunner can read query returns from the Integrated Public Number Database (IPND) and link the imported data (telephone numbers, names, addresses, contact names, connection/disconnection dates, Service Provider or Carrier details) to existing entities in the database. Many analysts find that this feature is a good a time-saver as CCR processing.
  • For Australian users, CallRunner will smoothly process Optus Web Traces - a format which includes multi-rows, out-of-sequence rows, Service Provider modification of IMEI numbers, and frequent use of engineering numbers.
  • Because all CCR data is stored, organised, and entities associated and linked in a robust Microsoft SQL Server database, the intelligence and investment in the processing remains accessible for months or years later (what may have appeared insignificant in the early days of an investigation is processed in just the same way as ostensibly important data).
  • CallRunner check-sum verifies imported IMEI numbers.  If the check-sum does not tally, the IMEI is flaged with a '?'.  More recently, some Service Providers substitute a zero for the last IMEI number (as in Optus Web Traces mentioned above).  CallRunner will replace the substituted zero with the correct number - determined by the check-sum formular.  CallRunner will flag the corrected IMEI number with a 'M' for Modified - see Screen Shots.
  • CallRunner will also use IMSI numbers, if included in CCR rows, to identify the country and the Service Provider during the import of a CCR.  There is also a feature for the user to look-up IMSI numbers to get the country, Service Provider, and subscriber ID code - see Screen Shots. 
  • CallRunner nominates missing area codes from dialled numbers by the cell tower locations.  (In Australia, it is not necessary to include the area code when dialling a land-line number for local calls.  However, if a mobile phone-user moves out of the subject area code, and dials a land-line number and does not include the area code - perhaps selected from a contact list stored in the phone - then a connection may be made to an unintended number in the moved-to area code region.  CallRunner will use the cell tower name to subustitute the new area code and colour-highlight the telephone number to notify the Analyst)
  • CallRunner Identifies and adjusts abbreviated cell tower and suburb names - such as 'Mrkvlle (Marrickville), 'N Caufld' (North Caufield), etc.
  • Uses a Post/Zipcode table to validate data entry of town and city names.
  • At address data entry points there is the facility to directly link to look-up web sites to verify town names and Zip/Postcodes.
  • Reads in, links, and saves user-prepared subscriber spreadsheet lists.  In this respect, over 3,000 State wide pay-phone numbers and locations were imported into CallRunner as lookup numbers for Victoria Police.
  • Reads in, links, and saves SIM card text product. Typical SIM contact names, such as 'Work', 'Mom', 'John', etc are stored as aliases until the subscriber name is determined and linked to the number.
  • Identifies the telephone exchange of imported land-line telephone numbers.
  • The content of many drop-down selection lists are user-definable.
  • CallRunner can be configured to link to an external database for telephone number lookup - as effected by NSW Police to their primary operational database (COPS).  In Australia, it can link to the Australia on Disk business directory to reverse retrieve subscriber details from an imported telephone number.
  • CallRunner can also be linked to the Electoral Roll to return greater detail of an imported subscriber, or to return the details of other people living at an address of a land-line who may therefore be potential users of the telephone.  In this process, the Electoral Roll accessed corresponds to the date of the imported telephone call.
  • Data is segregated and organised in user-defined 'Investigations'.  Staff are assigned to respective Investigators by an Administrator.
  • There are three levels of security which control access to segregated investigations and routines that users can perform.
  • CallRunner has a secure audit trail feature which can be configured by an Administrator to turn on, or off, the logging of a variety of user-actions.
  • Entity information (people, organisations, address, call records, telephone numbers, financial transactions etc) is linked and organised in tab folders so that associated entities can be easily located - see Screen Shots.
  • Processed information can be exported in a format for importtation into charting applications such as i2 Analyst or Watson.
  • CallRunner has its own basic charting presentation showing linked entities and chronologies (not intended to replace specialised charting applications).  See Screen Shots
  • Direct Google Maps links from address presentations, plus a Google Map report showing general locations of a mobile's telephone calls on a select day - see Screen Shots.
  • Ability to import and store location geocodes (latitude and longitude) for spatial analysis.
  • CallRunner has a database administration tool to effect database repairs and maintain relational and association integrity.
  • There are embedded 'How To' videos to assist users to learn application features.
  • Solid upkeep and maintenance program - with a stated objective for bug fixes and minor enhancements effected within twenty-four hours.
  • Runs on Windows XP, Vista, Windows 7