1. From the Tabs3 & PracticeMaster folder, double-click the Data Collection Device Conversion icon to start the Tabs3 Device Interface (TBDevice) software.
2. If the Logon dialog box is displayed, enter your User ID and Password and click OK.
3. From the File menu, select the Configure option.
4. The Configuration window will be displayed. Click the drop-down arrow next to the Device field and select Avaya.
5. In the File field, type the name of the file containing the data from the collection device (i.e., SMDR.csv).
6. Select the Default check box if you want to make the Avaya device the default in the Conversion program.
7. Click the drop-down arrow next to the Tcode field to select the transaction code number that you use for phone calls.
8. In the Rate field, specify the rate you want to use to calculate the amount for transactions.
9. Click the More Config button.
10. In the Descriptions section, select the Use Tcode Descriptions check box if you want the tcode description to be used in the cost transaction’s description field. Clear this check box if you want a blank transaction description instead. Select the Upper Case Text check box if the Use Tcode Descriptions check box is selected and you want to use all upper case letters in the cost transaction description.
11. Click OK.
12. Click the Save button.
13. Close the Configuration window.

1. Copy the file containing the data from the collection device (i.e., SMDR.csv) to the Tabs3 directory.
2. If the Tabs3 Device Interface (TBDevice) program is already started, skip to step 4. From the Tabs3 & PracticeMaster folder, double-click the Data Collection Device Conversion icon to start the Tabs3 Device Interface (TBDevice) program.
3. If the Logon dialog box is displayed, enter your User ID and Password and click OK.
4. From the File menu, select the Convert option.
5. The Conversion window will be displayed. If the Avaya device is not displayed in the Device field, click the drop-down arrow next to the Device field to select the Avaya format.
6. Verify that the file name to be converted is displayed in the File field.
7. Click the Convert button. The program will look for the file name specified in the Configuration window. If the file is found to contain data, the program will read transactions from the file and increment the Processed count for every transaction that is read. All transactions that are successfully converted will increment the Added count and will be written to the Tabs3 Remote data files (RMT*.*).
   
   Note: A TBDEVICE.LOG file is created and will contain any records that were not converted. If no errors were encountered during the conversion, then the TBDEVICE.LOG file will include a start and finish time.
   
   Note: If you are using a full user system, the data file containing the logged phone calls will automatically be deleted when the conversion is complete to avoid double posting of the data. However, when using a trial system, the data file is not deleted.
8. When the process is complete, the data files will have been created allowing you to merge the information into Tabs3 using the Merge Tabs3 Remote Data program. To merge the files, start Tabs3. From the Integration Task Folder, select Merge Tabs3 Remote Data. This program will merge the remote data files created by the Tabs3 Device Interface (TBDevice) program (RMT*.*) with your main Tabs3 data files. The Tabs3 Help includes complete details regarding the Merge Tabs3 Remote Data program.

• Each field is delimited by a comma.
• The Avaya Account field is converted as the Tabs3 Client ID. The decimal point will be inserted at the appropriate place based on your Tabs3 Decimal Places (i.e., Matter Length).
• The date portion of the Avaya Call Start field is converted as the Tabs3 Transaction Date.
• The Avaya call duration is converted as the Tabs3 units. The current format of the call duration is HH:MM:SS. It will be converted to HH.DD format. The DD portion is calculated by the addition of the minutes (MM divided by 60, since there are 60 minutes in an hour) and the seconds (SS divided by 3600, since there are 3600 seconds in an hour) and rounding up the nearest hundredth of an hour.
• Only transactions with an Avaya Direction code of "O" (which stands for outgoing calls) and an Is_Internal code of "0" (which stands for external calls) will be converted into Tabs3. All other calls will be skipped.

The following is an example of an Avaya SMDR.csv file. Please note that lines that were too long to fit on the page were wrapped to the next line and indented in this example so the text can be seen on the printed copy. Actual transactions in a real data file will appear as one continuous line.