When TIM Professional is configured to log calls from more than one telephone system, it distinguishes each site by its corresponding filename extension.

Initially, when data is transmitted to the call logger via TCP/IP, the software differentiates its various sites by the sender's IP address, which is then used to assign a filename extension to each site. Thereafter, the data is being sent to the  folder for processing and will log in the system within the site whose filename extension it corresponds to.

To assign a filename extension to a site, open the file from the main installation folder. An example of this is presented below.

All three sites are transmitting the data to the host application:

First, you need to assign a filename extensions to each site's IP address, in the TCPSOURCES.cfg file:

[TCP Data Sources]
 
192.168.0.29 = MBG
192.168.0.100 = FNC
192.168.0.54 = CNF

Next, you need to assign a name to each site, according to the filename extension above. Open the SITES.cfg file, located in the  folder within the main installation folder.

Under the section heading [All Sites], list each filename extension followed by an sign and the full name of the site as you would like to appear in reports. To instruct the software to interpret the data from a particular site using a different PBX data template, you need to specify the site name, followed by the the $ symbol and the template filename, as shown in the example below:

[All Sites]
 
MBG = Main Building
FNC = Financial Centre
CNF = Conference Building$Custom.tdt

In the example above, the Main Building and Financial Centre sites are configured to use the default PBX template file, e.g. Avaya IP Office.tdt, whilst the Conference Building site requires a custom template file, Custom.tdt.

Site 1 will send the data to TIM Professional, which will search for the IP address in the TCPSOURCES.cfg file and associate this with the extension MBG. A randomly named file will be created in the folder containing the data sent from the telephone system, e.g. . 

When the file is being picked up from the  folder, it can be identified successfully by the system as being sent from the site, as described in the SITES.cfg file.