These instructions help you configure your Avaya Network Alchemy to work with TIM Enterprise. Contact your system maintainer if you are not familiar with the configuration of your PBX.

<a id="Configure the SMDR output"></a>

Configuring your SMDR output

The Avaya Network Alchemy uses the Avaya Call Log software to configure the SMDR data. As the application will be outputting the data to a file, the installation of the Avaya Call Log software needs to be performed on the same machine as TIM Plus. A copy of the Avaya Call Log application can be found on your Avaya Administration CD. Your system maintainer should be able to supply you with a copy of the software.

The Avaya Call Log software does not run as a Windows Service; therefore, you must ensure that the application is never stopped because you may lose SMDR data.

Configuring Avaya Call Log

Follow the steps below to configure the Avaya Call Log software:

  1. Start the Avaya Call Log application.
  2. From the File menu, select Select Unit.
  3. In the first field, enter the IP address of your Avaya Network Alchemy.
  4. In the second field, enter the password for your Avaya Network Alchemy and click the OK button.
  5. From the File menu, select Log Option
  6. From the Select Logging Information window, choose the Periodic option.
  7. Type C:\Program Files\Tri-Line\TIM Enterprise\spool\data.{sitecode} in the Log Filename field, replacing {sitecode} with the ID of the site you are logging. To obtain the ID of a site, click on it and select Properties; the site ID will be displayed in the Unique ID field, as shown below:
  8. Click on the OK button to apply the settings.

Here is an example of how the Select Logging Information screen should appear:

<a id="Configure TIM Enterprise"></a>

 

 

 

<p>These instructions should assist in configuring your Avaya Network Alchemy to 
work with TIM Enterprise. If you are not familiar with PBX 
configuration, please contact your system maintainer.</p>

<table class="confluenceTable">
	<tbody>
		<tr>
			<th class="confluenceTh" width=158>Connection information</th>
			<th class="confluenceTh">Description</th>
		</tr>
		<tr>
			<td class="confluenceTd"><b>Connection type</b></td>
			<td class="confluenceTd">IP</td>
		</tr>
		<tr>
			<td class="confluenceTd"><b>IP Method</b></td>
			<td class="confluenceTd">You will need to install the Avaya Call Log which is available on your Administration CD. The Avaya Call Log will output SMDR data to a file.
			</td>
		</tr>
	</tbody>
</table>

<h2>Configuring your SMDR</h2>

<p>Below you will find instructions on how to configure the SMDR output for the Avaya Call Log.</p>

<h4>Obtaining & Configuring Avaya Call Log</h4>

<p>If you don't already have a copy of the Avaya Call Log, you can get a
 copy from the Administration CD. If you don't have this, you will 
need to speak to your system installer/maintainer and they should be 
able to supply you with it. The Avaya Call Log doesn't run as a 
service, so for you to receive all SMDR, the Avaya Call Log application 
needs to be running constantly and it needs to be on the same machine as 
TIM Enterprise.</p>

<p>Please follow the below instructions on how to configure the Avaya Call Log:</p>

<ol>
	<li>Start the Avaya Call Log application.</li>
	<li>Click on <span class="button no_margin">File</span> menu option and click on <span class="button no_margin">Select Unit</span>.</li>
	<li>In the first field enter the IP address of your Avaya Network Alchemy.</li>
	<li>In the second field enter the password for your Avaya Network Alchemy and click the <span class="button no_margin">OK</span> button.</li>
	<li>Click on <span class="button no_margin">File</span> menu option and click on <span class="button no_margin">Log Option</span> and the <span class="reference">Select Logging Information</span> window will open.</li>
	<li>Click on the <span class="keyword">Periodic</span> radio button.</li>
	<li>Now in the <span class="reference">Log Filename</span> field enter the following: <span class="keyword">C:\program file\tri-line\tim enterprise\spool\data.{sitecode}</span>. If you have used the installation wizard then 
	the <span class="keyword">sitecode</span> should be <span class="keyword">1</span>. If you haven't used the wizard, you can check the site code by browsing to TIM Enterprise, click on the 
	<span class="button no_margin">Directory</span> tab and hover over the site and the site code will appear.</li>
	<li>Click on the <span class="button no_margin">OK</span> button.</li>
</ol>

<p>Here is an example of how the <span class="reference">Select Logging Information</span> should be configured:</p>

<img class="screenshot" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_network_alchemy_1.png" alt="Avaya Network Alchemy" />

<h2>Configuring TIM Enterprise</h2>

<p>Below you will find steps on how to configure TIM Enterprise to listen for SMDR data from your Avaya Network Alchemy:</p>

<ol>
	<li>Browse to TIM Enterprise as normal and login with your credentials.</li>
	<li>Click on the <span class="button no_margin">Directory</span> tab.</li>
	<li>Go the the point in the Directory where you need to add the PBX Object and add a PBX with the name 'Avaya Network Alchemy'.</li>
	<li>Left-click on it and select <span class="button no_margin">Properties</span>.</li>
	<li>From the <span class="button no_margin">General</span> settings tab select <span class="keyword">Avaya Network Alchemy</span> from the PBX model list.</li>
	<img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_network_alchemy_2.png" alt="Avaya Network Alchemy" />
	<li>In the <span class="button no_margin">Connection</span> tab select <span class="keyword">No connection required</span> from the <span class="reference">Connection method</span> list.</li>
	<li>Finally, click on the <span class="button no_margin">Save</span> button.</li>
	<img class="screenshot border" src="http://www.tri-line.com/common/img/documentation/tim_enterprise/pbx/avaya_network_alchemy_3.png" alt="Avaya Network Alchemy" />
</ol>