Although TIM Professional can be configured to receive data from more than one telephone system, we strongly recommended our TIM Plus or Enterprise products for a multi-site system.

When TIM Professional is configured to log calls from more than one telephone system, TIM Professional 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 spool 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:

Site 1Site 2Site 3
Main Building
192.168.0.29		Financial Centre
192.168.0.100		Conference Building
192.168.0.54

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 assigned filename extension above. Open the SITES.CFG file, located in the \config folder within the main program 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. However, the Conference Building site requires a custom template file, Custom.tdt. The data from each site will be delivered to the \spool folder, using PBX and REM as the filename extensions  for the main and remote site, respectively.

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 is created in the spool folder containing the data sent from the telephone system, e.g. . 

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

All filenames are case-sensitive and the system will not be able to process the data if the expected characters are not used.

 

 

 

 

<p>Open the <span class="keyword">TCPSOURCES.CFG</span> file found in the  <span class="keyword">\config</span> folder within the main program folder.</p>

<p>In a multiple site situation, it is immaterial how the data from each site reaches the
<span class="keyword">\spool</span> folder, as long as it does get there.  What is important is the filename
extension of each site's data, as described in the previous
section.  This is because the software distinguishes each site by its
resultant file extension.</p>

<p>When data is transmitted to the software via TCP/IP, the software doesn't
automatically have a filename extension to give to the incoming data.
 The way the software differentiates its various sites is by the
sender's IP address.  Thus, the data is sent from a particular IP
address, this is corresponded to a filename extension and the data is
set in the <span class="keyword">\spool</span> folder with this filename extension.  The software 
can then identify the original site by this filename extension.</p>

<p>IP addresses and their corresponding filename extensions are set in the <span class="keyword">TCPSOURCES.CFG</span>
file, in the normal way.</p>

<p>For example, suppose we have three sites with the following IP addresses, all transmitting to
the host application:</p>

<table class="confluenceTable">
	<tbody>
		<tr>
			<th class="confluenceTh" width=120>Site 1</th>
			<th class="confluenceTh" width=120>Site 2</th>
			<th class="confluenceTh" width=120>Site 3</th>
		</tr>
		<tr>
			<td class="confluenceTd">Main Building<br/>192.168.0.29</td>
			<td class="confluenceTd">Financial Centre<br/>192.168.0.100</td>
			<td class="confluenceTd">Conference Building<br/>192.168.0.54</td>
		</tr>
	</tbody>
</table>

<p>We would first start by assigning filename extensions to the various IP addresses in the <span class="keyword">TCPSOURCES.CFG</span> file:</p>
[TCP Data Sources]

192.168.0.29 = MBG
192.168.0.100 = FNC
192.168.0.54 = CNF
<p>Then, in the <span class="keyword">SITES.CFG</span> file, as described previously, we would include each filename  extension as such:</p>
[All Sites]

MBG = Main Building
FNC = Financial Centre
CNF = Conference Building
<p>So, for example, Site 1 (the main building), IP address 192.168.0.29 transmits some data to
the host.  The host looks for the IP address in <span class="keyword">TCPSOURCES.CFG</span>
and finds the extension <span class="keyword">MBG</span>.  A randomly named file is created in the <span class="keyword">\spool</span>
folder containing the data that was sent, eg. 4de9380f.MBG.</p>

<p>When the software picks this file up from the spool folder, it can successfully identify that
the data was from the "Main Building", as described in the
<span class="keyword">SITES.CFG</span> file.</p>

NOTE: It is important to remember that all filename extensions are case-sensitive and that this is the first most likely cause of any problem in the system not identifying where data came from.