The first CLI Windows 95 based system was introduced in
1998 and replaced a Telstra development DOS based product which produced the
familiar blue screen image of CLI data in a very basic form. The application
suite was written in Visual Basic 5.
The CLI programs were designed to provide message
storage and printer facilities. In 1999 MTEL was approached to upgrade the CLI
suite for Y2K. MTEL named the new suite of programs CDAT to distinguish it from
CLI Win 95 programs. CDAT was coined from Calling Line Identification Data,
CLI-Data or CDAT.
The CDAT was upgraded again in 2005 with the new Windows
socket which took 5 years to debug. CDAT was upgraded to accept the new Telstra
IPND-MOLI format and the suite was released nationally to many ESO's around the
country through the Queensland Ambulance Service as CDAT 2006.
In early 2006 Telstra announced moves to deploy the CLI using
IP rather than X25. CDAT was upgraded to provide both services and was released
nationally again as CDAT 2008. This is the current nationally released product.
In 2010 Telstra released the dual feed IP for CLI. MTEL
was employed to produce applications to take both feeds and send a single CLI
into the CAD. At the same time the new Department of Community Safety which
incorporated the QAS introduced the CLI with the telephone service.
As a result of the new dual feed from Telstra MTEL was
employed to release two new products CDATServer and CDATHub
and these were operational in 2012.
CDATServer was introduced to provide multiple outputs
with a superset of the IPND packets from the original Telstra IPND packet. It
can also take multiple Telstra inputs and and route the packets to one or more
outputs using a simple tag matching process.
CDATHub is a rule based application which uses a set of
timers and a cache to decide which Telstra IP packet is sent to the CAD system.
The combination of the two products allow the DCS to
route redundant CLI packets from 14 centre's to a CAD system.
In 2013 the CDATServer product was replaced with the MIO product. It is the
same base product as the CDATServer however it has been renamed and changed to
reflect its true operation.
