Skip to main content
Kofax

ISDN FAX Tracing - Quick reference

Article # 3034883 - Page views: 59

Issue

For analyzing ISDN FAX problems there are different Tracing possibilities. This article describes:

  • What must be changed in the FAX channel configuration and in the registry to activate a specific trace
  • Which trace possibilities are available and where you find the resulting trace files.

Which kind of Trace is necessary for your specific problem, is evaluated by the Kofax Technical support representative analyzing your problem.

Solution

How do you change the Trace settings:

Basically there are two locations where FAX traces can be activated. In most cases you have to do changes in both locations.

  1. Changing the TraceFlags within the Registry:
    • Open regedit.exe
    • Navigate within regedit to the registry subkey:
      HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\LINK
    • For each connection to a KCS Lineserver you find here a separate registry registry sub key named LANxxx, where xxx is a numeric value specifying the so called node number.
    • In a first step we have to find out the node number for a specific KCS Line server.
    • The registry value LANxxx\IPToConnect specifies the IP address of the KCS Line server or of the machine running KCS Fax over IP.
      By checking all LANxxx subkeys you can find out therefore the Node number of a line server configured for a specific IP address.
      Example: registry value HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\LINK\LAN010\IPToConnect=10.1.2.3
      You know therefore that the KCS LS1 with IP address 10.1.2.3 uses the Node number LAN010 which is also labeled as L.10
    • Once you know the node number of a specific KCS LS1 navigate to
      HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags
    • Here you find the TraceFlags settings for a specific Node.
      Example 1: The TraceFlags settings for Node LAN010 (LS1)can be found in registry value
      HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags\Node_L.10.DSP0
      Example 2: The TraceFlags settings for Node LAN020 (Fax over IP node) can be found in registry value
      HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags\Node_L.20
    • Change the numeric value according to the recommendation given later in this article
      Example: If you want to activate ISDN, Modem and binary traces the Node_xxxx registry value must be set to the value 0x17 hexadecimal (=23 decmial)
    • Changes in the traceflag settings are automatically applied by TCOSS latest after 1 minute and do not require a TCOSS or node restart
    • Once the Traceflags are changed, the TCOSS trace shows a trace line like: N3/T04 727373=Traceflags changed from 0x0 to 0x17
       
  2. Changing the Trace settings within the FAX channel configuration file
    • Start the Maketcoss configuration program (WConfig
    • Enter the path where your TCOSS configuration is stored, e.g. C:\MT\KCSConfig
    • Select menu option Configure
    • Select menu option Single channel
    • Select the reference FAX channel for which you want to change the configuration, e.g. channel 10
    • Select menu option 9) line editor
    • Enter the configuration line which needs to be changed, which is typically 232, 242 or 32, please refer to the description later in this article
    • Change the configuration value according to the description later in this article and press OK to confirm the changes
    • If you have to change also another configuration line you can do this again entering the new configuration line number
    • Once you have changed all configuration lines, press Cancel to exist the line editor mode
    • Double click the E) Exit to exit the channel configuration
    • If you are asked to copy the configuration change to all channels which use the modified channel as reference channel, select the option Copy complete to to all channels which use this channel as reference. You will get a message box mentioning, how many channels have been changed.
    • Back to the channel list you can press the Exit button
    • Back to the Single channel menu option, press again the Exit button
    • Back to the main menu select the option Install configuration via net and press OK
    • provide the Path and the login creditials to your TCOSS system, for ASP TCOSS instances provide the TCOSSxx port in the path. Use a user who has the rights to write to the system folder (e.g. TCTECH user)
    • Press the Install button to install the configuration
    • After installing the changed configuration, you have to restart the Node in KCS Monitor or you have to reload the channel configuration
      • Open KCS Monitor and select the message server configured for your KCS system
      • Open the tree view showing the Nodes, select the correct Lan link node and select the menu option Tools - Reset/Reboot - Node or use the appropriate toolbar button
        clipboard_e19bb1791a7c3b32d0f02dcb572e720b6.png
         
Which Trace settings are necessary for a specific Type of trace.

The type of trace is requested by the Kofax Technical support representative. Following trace types are typically requested:

  • ISDN trace
    • Set the HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags\Node_xxx = 0x11 hexadecimal
    • Changes in the Traceflags are used by TCOSS without restarting TCOSS or the Node
    • ISDN Traces are included in the C:\TCOSS\Trace\TCOSS*.trc files
       
  • ISDN and MODEM Traces
    • Change the following configuration lines of the FAX channel configuration and apply the new configuration as described above:
      • Configuration line 232: 02 02 12 02
      • Configuration line 242: 00 00 00 03 8F 03 ...  (the remaining positions are not changed)
    • Set the HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags\Node_xxx = 0x13 hexadecimal
    • Restart the Node in KCS Monitor or restart TCOSS
    • ISDN and modem traces are included in the C:\TCOSS\Trace\TCOSS*.trc files
       
  • ISDN, MODEM and BINARY Traces
    • Change the following configuration lines of the FAX channel configuration and apply the new configuration as described above
      • Configuration line 232: 02 02 12 02
      • Configuration line 242: 00 00 00 03 8F 03 ...  (the remaining positions are not changed)
    • Set the HKLM\SOFTWARE\WOW6432Node\TOPCALL\TCOSS\TraceFlags\Node_xxx = 0x17 hexadecimal 
    • Restart the Node in KCS Monitor or restart TCOSS
    • ISDN and modem traces are included in the C:\TCOSS\Trace\TCOSS*.trc files
    • Binary traces are located in C:\TCOSS\Trace\TCOSS*.btr files
       
  • TAM/TUM Traces
    • Change the following configuration line of the FAX channel configuration and apply the new configuration as described above
      • Configuration line 32: 1
    • Select the corresponding channel in the channel list of the KCS Monitor message Server and reload the channel configuration:
      clipboard_e23916827dd844e9bf1876cd292037c2b.png
    • TAM/TUM Traces are included in the C:\TCOSS\Trace\TCOSS*.trc files
       
  • Journal files with extended information
    • Change the following configuration line of the FAX channel configuration and apply the new configuration as described above
      • Configuration line: 38: 0A 01
    • Select the corresponding channel in the channel list of the KCS Monitor message server and reload the channel configuration.
    • Journal files are text based log files can be found in the System folder of the KCS File structure (+MAIL5V folder). 
      • Outbound Journals are typically named AJyymmdd (yy=year, mm= month, dd=day, e.g. the Journal from 18th Oct. 2021 is named AJ211018)
      • Inbound Journals are typically named AIyymmdd (yy=year, mm= month, dd=day, e.g. the Journal from 18th Oct. 2021 is named AI211018)
  • BIT Error Rate Testing (BER)
    • This type of tracing possibility requires an ISDN line testing device (e.g. Aurora tester)
    • Change any free configuration line in the number conversion table of the FAX channel (Config line 254..283) and route to LOOPTEST.
      In the example below an inbound call to DDI number 9999 is configured to do an echo for BER Testing:
      • Configuraiton line 254: 39999=LOOPTEST
    • Restart the Node in KCS Monitor after changing and installing the configuration

 

Level of Complexity 

High

 

Applies to  

Product Version Build Environment Hardware
Kofax Communication Server TCOSS 10.x      

Keywords 

ISDN, analogue, BRI, PRI, E1, T1, TC23, TC24, TC26, TC30, TC31, TC32, Line Server, model, 305, Tracing FAX communication problems, Trace Setting, binary trace, modem trace

SO01
  • Was this article helpful?